AI agents call tani_resolve to retrieve information from Tani without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches/queries a registry to find tools matching an intent. It retrieves and ranks results but does not modify data, execute code, or cause side effects. It is a discovery/lookup operation.
From the tool's definition Find tools, APIs or MCP servers for an intent, ranked by computed invocation trust
Attacks that exploit this kind of access
Find tools, APIs or MCP servers for an intent, ranked by computed invocation trust. The meta-tool:. It is categorised as a Read tool in the Tani MCP Server, which means it retrieves data without modifying state.
Register the Tani MCP server in PolicyLayer and add a rule for tani_resolve: 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 Tani. Nothing to install.
tani_resolve 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 tani_resolve 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 tani_resolve. 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.
tani_resolve is provided by the Tani MCP server (naylalabs-org/tani-mcp). 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 →