text_count_occurrences
Count occurrences of a substring in text.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/text-count-occurrences.md
What text_count_occurrences does on UnClick
AI agents call text_count_occurrences to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | |
search | string | Yes | |
case_sensitive | boolean | — |
Parameters from the server's own tool schema.
Why text_count_occurrences is rated Low
The tool performs a read-only text search operation that returns a count. It has no side effects, does not execute code, does not modify data, and does not access external systems or financial resources. The blast radius of misuse is minimal—an agent could only learn information about text content that was already provided to it.
From the tool's definition Tool description: 'Count occurrences of a substring in text.' This is a query/analysis operation that retrieves information about text content without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs text_count_occurrences safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For text_count_occurrences, this is the rule to start with:
text_count_occurrences is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every text_count_occurrences call is checked against it from then on.
Questions about text_count_occurrences
Count occurrences of a substring in text. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
text_count_occurrences accepts 3 parameters: text, search, case_sensitive. Required: text, search. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for text_count_occurrences: 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 UnClick. Nothing to install.
text_count_occurrences 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 text_count_occurrences 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 text_count_occurrences. 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.
text_count_occurrences is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue