Test connectivity to the backend API.
AI agents call backend_connectivity_test to retrieve information from Tensorus MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a health check or connectivity verification tool that performs a query-like diagnostic operation. It does not create, modify, or delete data; it does not execute arbitrary code or trigger side effects; and it does not move money. The only effect is returning connectivity status information, which is a read-only operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'backend_connectivity_test' and description 'Test connectivity to the backend API' indicate a diagnostic/monitoring operation that retrieves or queries the status of backend connectivity without modifying, executing operations, or deleting data.
Attacks that exploit this kind of access
Test connectivity to the backend API. It is categorised as a Read tool in the Tensorus MCP MCP Server, which means it retrieves data without modifying state.
Register the Tensorus MCP server in PolicyLayer and add a rule for backend_connectivity_test: 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 Tensorus MCP. Nothing to install.
backend_connectivity_test 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 backend_connectivity_test 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 backend_connectivity_test. 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.
backend_connectivity_test is provided by the Tensorus MCP server (tensorus/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 →