AI agents call tani_governance 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 retrieves moderation audit/event data for inspection purposes only. It queries historical moderation events without side effects, altering data, or triggering external operations. The read-only nature (evidenced by 'recent...events' and 'verifications') and informational purpose place it firmly in the Read category with low severity, as misuse would only expose audit logs rather than cause operational harm.
From the tool's definition Tool returns 'recent moderation events — flags, drift, deprecations and signed verifications from the moderator fleet' with no capability to modify, delete, or execute operations.
Attacks that exploit this kind of access
Recent moderation events — flags, drift, deprecations and signed verifications from the moderator fleet. 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_governance: 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_governance 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_governance 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_governance. 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_governance 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 →