Test connection to Sure API.
AI agents call check_connection to retrieve information from Sure 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 non-destructive diagnostic tool that verifies API availability. It retrieves or queries the state of the connection (read operation) with no side effects, data modification, or external execution. Low severity because a failure to execute this check causes no harm, and success merely confirms availability without performing financial or destructive actions.
From the tool's definition Tool name is 'check_connection' and description states it 'Test[s] connection to Sure API' — a diagnostic operation that queries connectivity status without modifying, executing operations, or creating side effects.
Attacks that exploit this kind of access
Test connection to Sure API. It is categorised as a Read tool in the Sure MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sure MCP Server MCP server in PolicyLayer and add a rule for check_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 Sure MCP Server. Nothing to install.
check_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 check_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 check_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.
check_connection is provided by the Sure MCP Server MCP server (robcerda/sure-mcp-server). 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 →