AI agents call get_data_categories 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.
This tool appears to retrieve or list available data categories from Toronto's open data portal. It follows the naming and functional pattern of other Read-category tools in the sibling set. The empty description prevents full certainty, but the tool name and server context strongly indicate a simple query/retrieval operation with no side effects or data modification.
From the tool's definition Tool name 'get_data_categories' indicates retrieval of category information from the Toronto CKAN portal; sibling tools like 'list_datasets', 'search_datasets', 'get_package', and 'get_resource_records' are all data retrieval operations with no destructive…
Documented attack patterns abuse exactly the kind of access get_data_categories 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_data_categories:
{
"version": "1",
"default": "deny",
"tools": {
"get_data_categories": {}
}
}get_data_categories 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_data_categories. 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_data_categories: 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_data_categories 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_data_categories 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_data_categories. 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_data_categories 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.