AI agents call test_connection to retrieve information from Oitvoip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A connectivity test is a read-only diagnostic operation that performs no data operations, creates no resources, executes no code, and causes no state changes. The blast radius if misused is minimal — at worst, repeated calls might generate benign network traffic or logs. This fits the 'Read' category as a status check with no side effects.
From the tool's definition Tool name is 'test_connection' and description states it 'Test connectivity to NetSapiens API' — this is a diagnostic operation that checks if the API is reachable and responsive, with no data retrieval, modification, or side effects beyond confirming network…
Attacks that exploit this kind of access
Test connectivity to NetSapiens API. It is categorised as a Read tool in the Oitvoip MCP Server, which means it retrieves data without modifying state.
Register the Oitvoip 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 Oitvoip. 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 Oitvoip MCP server (oitapps/oitvoip-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 →