List available ontology release versions
AI agents call list_ontology_releases 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.
This is a straightforward informational lookup that retrieves a list of available versions. It has no side effects, cannot modify data, execute code, or cause destructive actions. The minimal blast radius and read-only nature justify low severity.
From the tool's definition Tool name 'list_ontology_releases' and description 'List available ontology release versions' indicate a query/retrieval operation that returns metadata about existing releases without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
List available ontology release versions. 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 list_ontology_releases: 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.
list_ontology_releases 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 list_ontology_releases 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 list_ontology_releases. 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.
list_ontology_releases 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 →