Test one configured integration endpoint: llm, embedding, ocr, document_parser, structure_recognition, postgres, zotero_mcp.
AI agents call test_integration_endpoint to retrieve information from Scifinder Route without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Testing an integration endpoint typically involves sending a probe request to verify configuration and connectivity, which is a read-like diagnostic operation with no data modification. However, depending on implementation, it could trigger side effects on external services. The description mentions only testing/verifying endpoints (llm, embedding, ocr, etc.), suggesting a read/ping operation.
From the tool's definition 'Test one configured integration endpoint' — this is a connectivity/health check operation
Attacks that exploit this kind of access
Test one configured integration endpoint: llm, embedding, ocr, document_parser, structure_recognition, postgres, zotero_mcp. It is categorised as a Read tool in the Scifinder Route MCP Server, which means it retrieves data without modifying state.
Register the Scifinder Route MCP server in PolicyLayer and add a rule for test_integration_endpoint: 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 Scifinder Route. Nothing to install.
test_integration_endpoint 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_integration_endpoint 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_integration_endpoint. 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_integration_endpoint is provided by the Scifinder Route MCP server (kettly1260/scifinder-route-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 →