Count characters, words, and lines in a block of text.
AI agents call word_count to retrieve information from Friday MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs purely informational analysis on provided text. It retrieves metrics (character count, word count, line count) without any destructive, executable, financial, or write capabilities. The operation is stateless and reversible in nature (though reversal is not needed). The low severity reflects minimal risk from misuse—an agent cannot cause harm with word counting functionality.
From the tool's definition Tool name 'word_count' and description 'Count characters, words, and lines in a block of text' indicate a read-only operation that analyzes text without modifying, executing code, deleting data, or causing side effects.
Attacks that exploit this kind of access
Count characters, words, and lines in a block of text. It is categorised as a Read tool in the Friday MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Friday MCP Server MCP server in PolicyLayer and add a rule for 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 Friday MCP Server. Nothing to install.
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 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 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.
word_count is provided by the Friday MCP Server MCP server (jeremylakeyjr/mcp-server). 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 →