Plan a bulk Codex install from a TokRepo user profile using the TokRepo CLI. Returns JSON dry-run output without writing files.
AI agents call tokrepo_clone_plan to retrieve information from TokRepo — AI Asset Registry without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only simulates/plans an install and returns JSON output without writing any files or executing any real changes. This is purely a read/query operation with no side effects, making it low severity.
From the tool's definition 'Plan a bulk Codex install' and 'Returns JSON dry-run output without writing files' — explicitly a dry-run that produces no side effects
Attacks that exploit this kind of access
Plan a bulk Codex install from a TokRepo user profile using the TokRepo CLI. Returns JSON dry-run output without writing files. It is categorised as a Read tool in the TokRepo — AI Asset Registry MCP Server, which means it retrieves data without modifying state.
Register the TokRepo — AI Asset Registry MCP server in PolicyLayer and add a rule for tokrepo_clone_plan: 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 TokRepo — AI Asset Registry. Nothing to install.
tokrepo_clone_plan is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tokrepo_clone_plan 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 tokrepo_clone_plan. 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.
tokrepo_clone_plan is provided by the TokRepo — AI Asset Registry MCP server (tokrepo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →