List available example ontology files
AI agents call list_example_files 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.
The tool performs a read-only operation to enumerate example files from an ontology documentation service. It has no side effects, does not execute code, does not modify data, and does not involve financial transactions. This is a straightforward information retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'list_example_files' and description 'List available example ontology files' indicate a query/listing operation that retrieves information without modifying state.
Attacks that exploit this kind of access
List available example ontology files. 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_example_files: 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_example_files 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_example_files 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_example_files. 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_example_files 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 →