List all resources (files) in a dataset with their formats and sizes.
AI agents call list_resources to retrieve information from Ontario Data without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only enumeration of dataset resources. It queries existing data structures to provide information about available files, analogous to 'list' or 'get' operations. There are no side effects, no code execution, no data modification, and no data deletion. The blast radius of misuse is minimal—an agent could only retrieve metadata about available resources.
From the tool's definition The tool 'list_resources' retrieves and displays metadata about dataset resources—their formats and sizes—without modifying, executing code, or performing destructive operations. This is a pure query/list operation.
Attacks that exploit this kind of access
List all resources (files) in a dataset with their formats and sizes. It is categorised as a Read tool in the Ontario Data MCP Server, which means it retrieves data without modifying state.
Register the Ontario Data MCP server in PolicyLayer and add a rule for list_resources: 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 Ontario Data. Nothing to install.
list_resources 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_resources 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_resources. 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_resources is provided by the Ontario Data MCP server (sprine/ontario-data-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 →