AI agents call cwiki_cache_info to retrieve information from CwikiMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and displays metadata about a local cache (its settings and size). It performs no write, delete, execute, or financial operations. The server is explicitly described as 'read-only' and this tool aligns with that design. The action is informational retrieval only, making it a Read category tool with low severity and high confidence.
From the tool's definition Tool name is 'cwiki_cache_info' and description states it 'Show[s] local Confluence response cache settings and current size' — purely a retrieval operation with no modification, deletion, or execution of external systems.
Attacks that exploit this kind of access
Show local Confluence response cache settings and current size. It is categorised as a Read tool in the CwikiMCP MCP Server, which means it retrieves data without modifying state.
Register the Cwiki MCP server in PolicyLayer and add a rule for cwiki_cache_info: 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 CwikiMCP. Nothing to install.
cwiki_cache_info 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 cwiki_cache_info 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 cwiki_cache_info. 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.
cwiki_cache_info is provided by the Cwiki MCP server (justinmclean/cwikimcp). 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 →