AI agents invoke kobold_abort to trigger actions in Kobold 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 triggers an external operation (aborting/cancelling an active generation process) on the KoboldAI server. It doesn't delete data permanently (not Destructive), doesn't write/create data, but it does interrupt and terminate a running process, which is an execution-level side effect. Misuse could disrupt legitimate generation tasks.
From the tool's definition Abort the currently ongoing generation
Documented attack patterns abuse exactly the kind of access kobold_abort gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kobold MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for kobold_abort:
{
"version": "1",
"default": "deny",
"tools": {
"kobold_abort": {
"limits": [
{
"counter": "kobold_abort_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}kobold_abort stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Abort the currently ongoing generation. It is categorised as a Execute tool in the Kobold MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kobold MCP Server MCP server in PolicyLayer and add a rule for kobold_abort: 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 Kobold MCP Server. Nothing to install.
kobold_abort 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 kobold_abort 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 kobold_abort. 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.
kobold_abort is provided by the Kobold MCP Server MCP server (phialsbasement/koboldcpp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kobold MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Kobold MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.