Inspect local files after a task and return an agent handoff packaging plan with quality_gate, package_manifest, SBOM-lite, and provenance. This is read-only and never publishes automatically; use tokrepo_push only after human confirmation with explicit reviewed files.
AI agents call tokrepo_handoff_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 explicitly states it is read-only and never publishes automatically. It inspects local files and produces a packaging plan (quality_gate, package_manifest, SBOM-lite, provenance) without executing any writes or deployments. The output is informational only, requiring explicit human confirmation before any publish action via a separate tool.
From the tool's definition 'This is read-only and never publishes automatically' and 'Inspect local files after a task and return an agent handoff packaging plan'
Attacks that exploit this kind of access
Inspect local files after a task and return an agent handoff packaging plan with quality_gate, package_manifest, SBOM-lite, and provenance. This is read-only and never publishes automatically; use tokrepo_push only after human confirmation with explicit reviewed 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_handoff_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_handoff_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_handoff_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_handoff_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_handoff_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 →