iam_issueAgentAct
Issue an agent ACT (POST /v1/iam/orgs/{org_id}/agents/{agent_did}/acts)
This record as markdown: /tools/onesi-genesis-mcp/iam-issueagentact.md
What iam_issueAgentAct does on Genesis
AI agents use iam_issueAgentAct to create or update resources in Genesis, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Genesis environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | Yes | |
org_id | string | Yes | The organization you are signed in to |
agent_did | string | Yes | The agent DID (did:oas:<kind>:<ulid>). This operation answers with the DID only, so it takes only the DID, not the a_ id. |
Parameters from the server's own tool schema.
Why iam_issueAgentAct is rated Medium
An AI agent can call iam_issueAgentAct faster than any human can review: one bad instruction and it creates or modifies resources in Genesis by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs iam_issueAgentAct safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For iam_issueAgentAct, this is the rule to start with:
iam_issueAgentAct stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Genesis, apply this rule, and every iam_issueAgentAct call is checked against it from then on.
Questions about iam_issueAgentAct
Issue an agent ACT (POST /v1/iam/orgs/{org_id}/agents/{agent_did}/acts). It is categorised as a Write tool in the Genesis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
iam_issueAgentAct accepts 3 parameters: body, org_id, agent_did. Required: body, org_id, agent_did. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for iam_issueAgentAct: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Genesis. Nothing to install.
iam_issueAgentAct is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the iam_issueAgentAct rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for iam_issueAgentAct. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
iam_issueAgentAct is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
This server
Across the catalogue