Write raw text into a workspace inbox.
AI agents use knowledge_ingest_text to create or update resources in Chisel Knowledge MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Chisel Knowledge MCP environment.
This tool creates or appends text data to a workspace inbox, which is a reversible operation. It modifies state within the knowledge workspace but does not execute arbitrary code, delete data irreversibly, or involve financial transactions. The low severity reflects that the blast radius of misuse is contained within a single workspace inbox with no destructive or systemic consequences.
From the tool's definition Tool name and description explicitly state 'Write raw text into a workspace inbox' - the verb 'Write' and action 'ingest' indicate data creation/modification into a designated inbox location.
Attacks that exploit this kind of access
Write raw text into a workspace inbox. It is categorised as a Write tool in the Chisel Knowledge MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Chisel Knowledge MCP server in PolicyLayer and add a rule for knowledge_ingest_text: 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 Chisel Knowledge MCP. Nothing to install.
knowledge_ingest_text 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 knowledge_ingest_text 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 knowledge_ingest_text. 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.
knowledge_ingest_text is provided by the Chisel Knowledge MCP server (teknologika/chisel-knowledge-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 →