Test connectivity to the ontology file server
AI agents call test_ontology_server to retrieve information from Earth616 Vocabulary Service without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Testing connectivity is a read-only operation that retrieves status information from the server. It has no side effects, cannot modify or delete data, and its worst-case misuse is negligible (minor network noise). Severity is low because even repeated misuse causes minimal impact.
From the tool's definition 'Test connectivity to the ontology file server' — this is a diagnostic/ping operation that checks server reachability without modifying any data.
Attacks that exploit this kind of access
Test connectivity to the ontology file server. It is categorised as a Read tool in the Earth616 Vocabulary Service MCP Server, which means it retrieves data without modifying state.
Register the Earth616 Vocabulary Service MCP server in PolicyLayer and add a rule for test_ontology_server: 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 Earth616 Vocabulary Service. Nothing to install.
test_ontology_server 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_ontology_server 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_ontology_server. 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_ontology_server is provided by the Earth616 Vocabulary Service MCP server (la3d/mcp_vocabulary_service). 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 →