Count regex pattern matches in a wikitext string.
AI agents call get_any_count to retrieve information from Wikicitation without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool analyzes wikitext by matching a regex pattern and returning a count. It is purely informational—it reads and counts without creating, modifying, deleting, or executing any external operations. The blast radius of misuse is negligible; an AI agent could only receive an incorrect count or be delayed by expensive regex operations, not cause data corruption or security breaches.
From the tool's definition Tool description: 'Count regex pattern matches in a wikitext string.' The verb 'count' is a retrieval/analysis operation with no side effects. It returns a count result based on input wikitext without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Count regex pattern matches in a wikitext string. It is categorised as a Read tool in the Wikicitation MCP Server, which means it retrieves data without modifying state.
Register the Wikicitation MCP server in PolicyLayer and add a rule for get_any_count: 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 Wikicitation. Nothing to install.
get_any_count 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 get_any_count 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 get_any_count. 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.
get_any_count is provided by the Wikicitation MCP server (jsobel1/wikicitation-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 →