Fetch a token via POST /tokens using env ZENTAO_ACCOUNT/PASSWORD. Caches in-memory.
AI agents call get_token to retrieve information from ZenTao MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although this uses POST, the tool's purpose is to retrieve (read) an authentication token for subsequent API use. It has no side effects on data or system state—it merely obtains credentials. The in-memory caching is a client-side optimization.
From the tool's definition Tool fetches/retrieves a token via POST to /tokens endpoint. The description states 'Fetch a token' which is a retrieval operation.
Attacks that exploit this kind of access
Fetch a token via POST /tokens using env ZENTAO_ACCOUNT/PASSWORD. Caches in-memory. It is categorised as a Read tool in the ZenTao MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ZenTao MCP Server MCP server in PolicyLayer and add a rule for get_token: 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 ZenTao MCP Server. Nothing to install.
get_token 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 get_token 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 get_token. 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.
get_token is provided by the ZenTao MCP Server MCP server (valiant-cat/zentao-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 →