AI agents call get_word_count to retrieve information from Markview without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs analysis and retrieval of statistical information about markdown content. It has no side effects, makes no modifications to data, executes no code, and cannot delete or move money. It is a pure read operation that returns computed metrics. The low severity reflects that misuse would only expose trivial information about file size metrics.
From the tool's definition Tool is named 'get_word_count' and described as counting words, characters, lines, and estimated tokens in markdown content. These are all read-only operations that query and retrieve metrics from content without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Count words, characters, lines, and estimated tokens in markdown content. It is categorised as a Read tool in the Markview MCP Server, which means it retrieves data without modifying state.
Register the Markview MCP server in PolicyLayer and add a rule for get_word_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 Markview. Nothing to install.
get_word_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_word_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_word_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_word_count is provided by the Markview MCP server (mcp-server-markview). 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 →