Call any ZenTao RESTful API endpoint (api.php/v1). Automatically injects Token header. Paths accept leading slash or relative.
AI agents invoke call to trigger actions in ZenTao MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool can invoke any RESTful API endpoint on the ZenTao system, including destructive operations (DELETE), financial commitments, or arbitrary writes. Because it is a generic executor with no restrictions on HTTP method or path, the most severe applicable category is Execute (potentially Destructive or Financial depending on arguments).
From the tool's definition 'Call any ZenTao RESTful API endpoint' — arbitrary API call with automatic token injection, accepting any path and method
Attacks that exploit this kind of access
Call any ZenTao RESTful API endpoint (api.php/v1). Automatically injects Token header. Paths accept leading slash or relative. It is categorised as a Execute tool in the ZenTao MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ZenTao MCP Server MCP server in PolicyLayer and add a rule for call: 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.
call is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the call 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 call. 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.
call 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 →