AI agents call get_resource_records to retrieve information from Toronto MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and server purpose (querying and retrieving datasets from a public CKAN portal) strongly suggest this retrieves data without modification. No execution, deletion, or financial operations are implied. Low severity because open data portals typically contain public information with no sensitive side effects from retrieval.
From the tool's definition Tool name 'get_resource_records' and server context indicate data retrieval from Toronto's open data portal. Sibling tools (get_first_datastore_resource_records, get_dataset_insights, search_datasets) are all Read operations.
Documented attack patterns abuse exactly the kind of access get_resource_records gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Toronto MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_resource_records:
{
"version": "1",
"default": "deny",
"tools": {
"get_resource_records": {}
}
}get_resource_records is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_resource_records. It is categorised as a Read tool in the Toronto MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Toronto MCP Server MCP server in PolicyLayer and add a rule for get_resource_records: 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 Toronto MCP Server. Nothing to install.
get_resource_records 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 get_resource_records 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 get_resource_records. 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.
get_resource_records is provided by the Toronto MCP Server MCP server (toronto-inc/toronto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Toronto MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Toronto MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.