AI agents use wiki_save to create or update resources in Llama — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Llama environment.
The tool enables creation and modification of wiki content, which are Write-category actions. Severity is medium because wiki modifications affect documentation/knowledge shared across the platform and could introduce misinformation if misused by an agent, but changes are typically reversible through version history or restoration features (as suggested by sibling tools like brief_history and brief_restore).
From the tool's definition Tool description states 'Create or update a wiki page' — these are reversible write operations that modify data on the Llama Ventures platform without permanently destroying it.
Attacks that exploit this kind of access
Create or update a wiki page — Llama. It is categorised as a Write tool in the Llama MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Llama MCP server in PolicyLayer and add a rule for wiki_save: 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 Llama. Nothing to install.
wiki_save 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 wiki_save 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 wiki_save. 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.
wiki_save is provided by the Llama MCP server (llama-ventures/llama-cli). 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 →