AI agents call list_wikis to retrieve information from Llm Wiki without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries metadata (wiki names) without creating, modifying, deleting, or executing any operations. It is a straightforward enumeration action with no side effects, fitting the Read category.
From the tool's definition Tool name 'list_wikis' and description 'List all wiki names' indicate a retrieval operation with no modification of data.
Attacks that exploit this kind of access
List all wiki names. It is categorised as a Read tool in the Llm Wiki MCP Server, which means it retrieves data without modifying state.
Register the Llm Wiki MCP server in PolicyLayer and add a rule for list_wikis: 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.
list_wikis is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_wikis 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 list_wikis. 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.
list_wikis 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.
list_wikis is one line of Llm Wiki's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →