AI agents call list_tenants to retrieve information from Docs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool lists tenants in a multi-tenant documentation server, which is a read operation with no side effects. The blast radius is minimal—enumeration of tenant identifiers poses limited risk compared to direct data access or destructive operations.
From the tool's definition Tool name 'list_tenants' indicates enumeration of tenant objects. Server description states tools are exposed for 'search and fetch' operations.
Attacks that exploit this kind of access
list_tenants. It is categorised as a Read tool in the Docs MCP Server, which means it retrieves data without modifying state.
Register the Docs MCP server in PolicyLayer and add a rule for list_tenants: 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 Docs. Nothing to install.
list_tenants 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 list_tenants 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 list_tenants. 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.
list_tenants is provided by the Docs MCP server (pankaj28843/docs-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 →