Get a single HelloGrowthCRM changelog release by version (e.g. 1.5.0) with its full list of tagged items.
AI agents call changelog_get_release 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.
The tool performs a read-only retrieval of version history data. It does not modify, delete, or execute any operations. No authentication bypass, data exposure, or unintended effects are plausible from misuse of a changelog query.
From the tool's definition Tool retrieves changelog information: 'Get a single HelloGrowthCRM changelog release by version... with its full list of tagged items.' This is a query/fetch operation with no side effects.
Attacks that exploit this kind of access
Get a single HelloGrowthCRM changelog release by version (e.g. 1.5.0) with its full list of tagged items. 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 changelog_get_release: 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.
changelog_get_release 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 changelog_get_release 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 changelog_get_release. 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.
changelog_get_release 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 →