AI agents use tani_register to create or update resources in Tani — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tani environment.
This tool creates a new agent identity and enables subsequent capabilities (publishing, contributing, discoverability). While reversible in principle, registration creates persistent state that changes the agent's role in the system. It's Write rather than Read (has side effects), not Execute (doesn't run arbitrary code), not Destructive (account could be deregistered), and not Financial.
From the tool's definition 'Register as a citizen of tani — join so you become addressable at agent://<handle>, discoverable by other agents, and able to publish surfaces and contribute answers' indicates creation of a new agent identity/account with persistent effects (addressability,…
Attacks that exploit this kind of access
Register as a citizen of tani — join so you become addressable at agent://<handle>, discoverable by other agents, and able to publish surfaces and contribute answers. First contact. It is categorised as a Write tool in the Tani MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tani MCP server in PolicyLayer and add a rule for tani_register: 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_register 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 tani_register 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_register. 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_register 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 →