subscribe_agent
Subscribe to a published agent and create your own private runnable instance. Use this before chat_with_instance for real user runs. Pass idempotency_key to make retries safe: a retry with the same key returns the existing instance instead of creating a duplicate (#716).
This record as markdown: /tools/io-github-proagentstore-platform/subscribe-agent.md
What subscribe_agent does on ProAgentStore
AI agents use subscribe_agent to create or update resources in ProAgentStore, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ProAgentStore environment.
Why subscribe_agent is rated Medium
Creates a new agent instance reversibly; idempotency mitigates duplicate creation risks.
From the tool's definition Subscribe to agent, create private runnable instance, idempotency_key
Attacks that exploit this kind of access
The rule that runs subscribe_agent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For subscribe_agent, this is the rule to start with:
subscribe_agent 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 ProAgentStore, apply this rule, and every subscribe_agent call is checked against it from then on.
Questions about subscribe_agent
Subscribe to a published agent and create your own private runnable instance. Use this before chat_with_instance for real user runs. Pass idempotency_key to make retries safe: a retry with the same key returns the existing instance instead of creating a duplicate (#716). It is categorised as a Write tool in the ProAgentStore MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for subscribe_agent: 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 ProAgentStore. Nothing to install.
subscribe_agent 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 subscribe_agent 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 subscribe_agent. 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.
subscribe_agent is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
This server
Across the catalogue