Test the connection to the GraphQL endpoint.
AI agents call test_connection to retrieve information from MCP GraphQL Sales Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A connection test is a diagnostic operation that typically sends a minimal query or ping to verify availability and network connectivity. It retrieves status information but does not create, modify, delete, or execute operations on the underlying sales database. This is a benign read-category operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name and description indicate a connection test operation. Testing a connection to an endpoint performs a read-only probe with no data modification, deletion, or code execution.
Attacks that exploit this kind of access
Test the connection to the GraphQL endpoint. It is categorised as a Read tool in the MCP GraphQL Sales Server MCP Server, which means it retrieves data without modifying state.
Register the MCP GraphQL Sales 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 MCP GraphQL Sales 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 MCP GraphQL Sales Server MCP server (jambelg/mcp-graphql-claude). 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 →