Fetch a single contact form submission by ID.
AI agents call forms_get_submission 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 retrieves existing form submission data by identifier. The verb 'fetch' and structure indicate a read-only query operation with no capability to modify, delete, or execute actions. The data retrieved (contact form submissions) may contain user information, but access control and data sensitivity would be governed by application-level permissions rather than the tool's functional category.
From the tool's definition Tool name 'forms_get_submission' and description 'Fetch a single contact form submission by ID' indicate retrieval of data without modification or side effects.
Attacks that exploit this kind of access
Fetch a single contact form submission by ID. 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 forms_get_submission: 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.
forms_get_submission 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 forms_get_submission 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 forms_get_submission. 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.
forms_get_submission 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 →