AI agents use ingest to create or update resources in Llm Wiki — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Llm Wiki environment.
The server description explicitly mentions ingestion as a core capability, suggesting this tool writes/imports documents into the wiki knowledge base. The name 'ingest' universally refers to data import/loading operations. However, the empty description lowers confidence, and without knowing if it overwrites existing data, Write is the most appropriate category at medium severity.
From the tool's definition Tool name 'ingest' implies importing or loading data into the system; server description mentions 'ingestion of wiki knowledge bases built from documents'
Attacks that exploit this kind of access
ingest. It is categorised as a Write tool in the Llm Wiki MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Llm Wiki MCP server in PolicyLayer and add a rule for ingest: 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 Llm Wiki. Nothing to install.
ingest 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 ingest 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 ingest. 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.
ingest is provided by the Llm Wiki MCP server (quick-sort/llm-wiki-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 →