Resolve the full provenance tree for an AR-ID. Returns every anchor in the tree (root + all descendants) with their relationships, types, manifest hashes, and timestamps. Use this when you need to understand a multi-artifact provenance chain — for example, a research paper anchored as the root wi...
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Part of the AnchorRegistry server.
Free to start. No card required.
AI agents use ar_resolve_tree to create or modify resources in AnchorRegistry. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call ar_resolve_tree repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AnchorRegistry.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"ar_resolve_tree": {
"limits": [
{
"counter": "ar_resolve_tree_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full AnchorRegistry policy for all 3 tools.
These attack patterns abuse exactly the kind of access ar_resolve_tree gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Resolve the full provenance tree for an AR-ID. Returns every anchor in the tree (root + all descendants) with their relationships, types, manifest hashes, and timestamps. Use this when you need to understand a multi-artifact provenance chain — for example, a research paper anchored as the root with its training dataset and model weights as children.. It is categorised as a Write tool in the AnchorRegistry MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AnchorRegistry MCP server in PolicyLayer and add a rule for ar_resolve_tree: 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 AnchorRegistry. Nothing to install.
ar_resolve_tree is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ar_resolve_tree 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 ar_resolve_tree. 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.
ar_resolve_tree is provided by the AnchorRegistry MCP server (https://mcp.anchorregistry.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 AnchorRegistry 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.