AI agents invoke tickiti_call to trigger actions in Tickiti. 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 functions as a generic pass-through to arbitrary API endpoints, which falls under Execute category. Its capability to invoke any endpoint means it could be weaponized to perform Write, Destructive, or even Financial operations depending on what the Tickiti API supports and what arguments an agent provides.
From the tool's definition Tool name is 'tickiti_call' with description stating it is an 'Advanced escape hatch: invoke any Tickiti v1 endpoint not covered by a [other tools]'.
Attacks that exploit this kind of access
Advanced escape hatch: invoke any Tickiti v1 endpoint not covered by a. It is categorised as a Execute tool in the Tickiti MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tickiti MCP server in PolicyLayer and add a rule for tickiti_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 Tickiti. Nothing to install.
tickiti_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 tickiti_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 tickiti_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.
tickiti_call is provided by the Tickiti MCP server (tickiti/tickiti-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 →