run_capability
Run one exact capability through the governed dispatcher. Defaults to preview for every call. Set dryRun:false to execute reads, including paid provider reads and enrichment. Live writes remain subject to server-bound approval, reason, policy, and idempotency controls. Product profiles refuse ref...
This record as markdown: /tools/adrata-adrata-mcp/run-capability.md
What run_capability does on Adrata
AI agents invoke run_capability to trigger actions in Adrata. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why run_capability is rated High
run_capability triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs run_capability safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_capability, this is the rule to start with:
run_capability stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Adrata, apply this rule, and every run_capability call is checked against it from then on.
Questions about run_capability
Run one exact capability through the governed dispatcher. Defaults to preview for every call. Set dryRun:false to execute reads, including paid provider reads and enrichment. Live writes remain subject to server-bound approval, reason, policy, and idempotency controls. Product profiles refuse references outside their namespace. It is categorised as a Execute tool in the Adrata MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Adrata MCP server in PolicyLayer and add a rule for run_capability: 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 Adrata. Nothing to install.
run_capability is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_capability 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 run_capability. 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.
run_capability is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adrata, and thousands of servers like it.
Across the catalogue