Permit.io ACTION
Assign Role
Grants a specific role to a user within a tenant to enable immediate access to protected resources. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Permit.io account once, then configure and run Assign Role from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "permit_io-assign-role",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
permit_io: { authProvisionId: "apn_xxxxxxx" },
projId: "Project ID",
envId: "Environment ID",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "permit_io-assign-role",
"configured_props": {
"permit_io": { "authProvisionId": "apn_xxxxxxx" },
"projId": "Project ID",
"envId": "Environment ID"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "permit_io",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "permit_io-assign-role",
arguments: {
projId: "Project ID",
envId: "Environment ID",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
projId Project ID | string | The project key or ID Required Dynamic |
envId Environment ID | string | The environment key or ID Required Dynamic |
role Role | string | The role key or ID (e.g. admin, editor) Required Dynamic |
user User | string | The user key or ID (e.g. jane@example.com) Required Dynamic |
tenant Tenant | string | The tenant key or ID (e.g. stripe-inc) Optional Dynamic |
resourceInstance Resource Instance | string | The resource instance the role is associated with. Use the format resource_type:resource_instance_key (e.g. repo:opal). The instance will be implicitly created if Tenant is specified and it does not exist. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- permit_io-assign-role
- Version
- 0.0.2
- App
- Permit.io
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗