Stable tool entrypoint for Kunobi operations. Call a variant tool via (variant, tool, arguments), e.g. variant=
AI agents invoke kunobi_call to trigger actions in Kunobi 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 acts as a meta-executor that dispatches calls to other tools by name with arbitrary arguments. Since it can invoke any tool on the Kunobi server (including data-modifying or execution operations like query_store), the most severe applicable category is Execute.
From the tool's definition 'Stable tool entrypoint for Kunobi operations. Call a variant tool via (variant, tool, arguments)' — this is a generic dispatcher that can invoke arbitrary tools including query_store and app_info
Attacks that exploit this kind of access
Stable tool entrypoint for Kunobi operations. Call a variant tool via (variant, tool, arguments), e.g. variant=. It is categorised as a Execute tool in the Kunobi MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kunobi MCP Server MCP server in PolicyLayer and add a rule for kunobi_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 Kunobi MCP Server. Nothing to install.
kunobi_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 kunobi_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 kunobi_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.
kunobi_call is provided by the Kunobi MCP Server MCP server (kunobi-ninja/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 →