A simple test tool to verify MCP connection is working
AI agents call test_connection to retrieve information from Webflow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a lightweight diagnostic tool that checks connectivity status. It has no side effects, does not retrieve meaningful data beyond connection state, and does not modify any resources. It falls cleanly into the Read category with low severity due to its minimal scope and informational purpose only.
From the tool's definition Tool name 'test_connection' and description 'A simple test tool to verify MCP connection is working' indicate a diagnostic operation that retrieves connection status without modifying data.
Attacks that exploit this kind of access
A simple test tool to verify MCP connection is working. It is categorised as a Read tool in the Webflow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Webflow MCP Server MCP server in PolicyLayer and add a rule for test_connection: 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 Webflow MCP Server. Nothing to install.
test_connection 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 test_connection 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 test_connection. 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.
test_connection is provided by the Webflow MCP Server MCP server (timkjones/mcp-webflow). 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 →