kb_write_content
A write tool on the Container- MCP server.
This record as markdown: /tools/54rt1n-container-mcp/kb-write-content.md
What kb_write_content does on Container-MCP
AI agents use kb_write_content to create or update resources in Container-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Container-MCP environment.
Why kb_write_content is rated Medium
The 'kb_write_content' tool creates or modifies data within a knowledge base (reversible operation). While the description is uninformative, the name and context of sibling kb_* tools strongly suggest data modification capabilities. Classified as Write rather than Destructive since it appears to modify content rather than irreversibly delete it.
From the tool's definition Tool name 'kb_write_content' indicates writing/modification of knowledge base content. Description is empty, limiting certainty. Sibling tools include kb_create_document and kb_manage, suggesting this server manages knowledge base operations.
Attacks that exploit this kind of access
The rule that runs kb_write_content safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Container-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kb_write_content, this is the rule to start with:
kb_write_content 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Container-MCP, apply this rule, and every kb_write_content call is checked against it from then on.
Questions about kb_write_content
kb_write_content is a write tool on the Container MCP server. It is categorised as a Write tool in the Container-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Container MCP server in PolicyLayer and add a rule for kb_write_content: 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 Container-MCP. Nothing to install.
kb_write_content 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 kb_write_content 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 kb_write_content. 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.
kb_write_content is provided by the Container MCP server (54rt1n/container-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Container, and thousands of servers like it.
This server
Across the catalogue