AI agents call kanka_get_campaign to retrieve information from Kanka without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves campaign metadata without modifying, deleting, or executing any operations. It is a straightforward query operation with minimal blast radius if misused by an AI agent—at worst, an attacker gains access to campaign metadata they may not be authorized to see, which is a confidentiality concern but not destructive or financial.
From the tool's definition Tool name 'kanka_get_entity' and description 'Fetch metadata for a single campaign by id' indicate a retrieval operation with no side effects. The verb 'Fetch' is explicitly a read-only action.
Attacks that exploit this kind of access
Fetch metadata for a single campaign by id. It is categorised as a Read tool in the Kanka MCP Server, which means it retrieves data without modifying state.
Register the Kanka MCP server in PolicyLayer and add a rule for kanka_get_campaign: 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 Kanka. Nothing to install.
kanka_get_campaign 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 kanka_get_campaign 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 kanka_get_campaign. 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.
kanka_get_campaign is provided by the Kanka MCP server (torinvdb/kanka-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 →