List all distinct blog categories present in the database.
AI agents call blog_get_categories to retrieve information from Mcp Bot Crawler without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns blog category data without creating, modifying, or deleting any information. It is a simple read operation that retrieves metadata about existing blog categories. The low severity reflects minimal risk even if misused by an AI agent, as it only exposes category names without sensitive data exposure or operational impact.
From the tool's definition Tool name 'blog_get_categories' and description 'List all distinct blog categories present in the database' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all distinct blog categories present in the database. It is categorised as a Read tool in the Mcp Bot Crawler MCP Server, which means it retrieves data without modifying state.
Register the Mcp Bot Crawler MCP server in PolicyLayer and add a rule for blog_get_categories: 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 Mcp Bot Crawler. Nothing to install.
blog_get_categories 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 blog_get_categories 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 blog_get_categories. 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.
blog_get_categories is provided by the Mcp Bot Crawler MCP server (merulocal/hellogrowthcrmwebsite_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 →