Read the asset relationship graph for one asset. Returns inbound + outbound edges across requires (hard deps), extends (soft pairings), and co_used (behavior-derived co-installs). Use this BEFORE planning installs to discover related assets and avoid solo installs of assets that pair with others.
AI agents call tokrepo_edges 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.
tokrepo_edges retrieves and queries relationship metadata for AI assets without modifying data, triggering external operations, or permitting deletions. This is a pure read/query operation with minimal blast radius if misused—an AI agent calling it repeatedly or with invalid inputs would simply receive no useful data or errors, with no side effects.
From the tool's definition The tool explicitly 'Read[s] the asset relationship graph for one asset.' The description emphasizes retrieval with 'Returns inbound + outbound edges' and provides no write, execute, or destructive capabilities.
Attacks that exploit this kind of access
Read the asset relationship graph for one asset. Returns inbound + outbound edges across requires (hard deps), extends (soft pairings), and co_used (behavior-derived co-installs). Use this BEFORE planning installs to discover related assets and avoid solo installs of assets that pair with others. 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_edges: 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_edges 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_edges 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_edges. 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_edges 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 →