AI agents use create_kibela_comment to create or update resources in Kibela MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kibela MCP Server environment.
This tool creates new comment objects in Kibela, which is a reversible modification operation (comments can typically be edited or deleted). It does not execute arbitrary code, delete data irreversibly, or move money. It falls squarely in the Write category.
From the tool's definition Tool name 'create_kibela_comment' indicates creation of new content (comments) in the Kibela knowledge base system.
Documented attack patterns abuse exactly the kind of access create_kibela_comment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kibela MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_kibela_comment:
{
"version": "1",
"default": "deny",
"tools": {
"create_kibela_comment": {
"limits": [
{
"counter": "create_kibela_comment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_kibela_comment stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create_kibela_comment. It is categorised as a Write tool in the Kibela MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kibela MCP Server MCP server in PolicyLayer and add a rule for create_kibela_comment: 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 Kibela MCP Server. Nothing to install.
create_kibela_comment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_kibela_comment 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 create_kibela_comment. 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.
create_kibela_comment is provided by the Kibela MCP Server MCP server (kibela/kibela-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kibela 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.
18 Kibela MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.