Run a specific named Alexandria agent directly on a task. Use this when you know exactly which specialist you want (e.g., "brand-copywriter", "senior-developer"). Supports two modes (auto-selected via ALEXANDRIA_MODE): (1) DELEGATE — returns the agent's assembled prompt + context + learnings for ...
Risk signalsAccepts file system path (files[].path) · Accepts raw HTML/template content (files[].content)
Part of the Alexandria server.
Free to start. No card required.
AI agents invoke alexandria_run_agent to trigger processes or run actions in Alexandria. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
alexandria_run_agent can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"alexandria_run_agent": {
"limits": [
{
"counter": "alexandria_run_agent_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Alexandria policy for all 20 tools.
These attack patterns abuse exactly the kind of access alexandria_run_agent gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Run a specific named Alexandria agent directly on a task. Use this when you know exactly which specialist you want (e.g., "brand-copywriter", "senior-developer"). Supports two modes (auto-selected via ALEXANDRIA_MODE): (1) DELEGATE — returns the agent's assembled prompt + context + learnings for your next reply to execute. Zero cost, uses your Claude Code subscription. (2) BYOT EXECUTE — runs the agent against your provider key and returns the finished output. Supports optional file context injection for code review, modification, or analysis tasks. For automatic agent selection, use alexandria_ask instead.. It is categorised as a Execute tool in the Alexandria MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Alexandria MCP server in PolicyLayer and add a rule for alexandria_run_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 Alexandria. Nothing to install.
alexandria_run_agent 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 alexandria_run_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 alexandria_run_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.
alexandria_run_agent is provided by the Alexandria MCP server (mcp-server-alexandria). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 20 Alexandria tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.