query_tunnels
AI agents call query_tunnels to retrieve information from Government of Canada Open Data MCP Servers without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries tunnel infrastructure data from open Canadian government datasets. Query operations on public government data retrieves information without side effects, making it a Read category tool. Low severity due to the public nature of the datasets and lack of capacity to modify, delete, or execute operations.
From the tool's definition Tool name 'query_tunnels' indicates a query operation on tunnel infrastructure data. The server is described as providing 'access to' and 'querying of' Canadian government datasets.
Attacks that exploit this kind of access
query_tunnels. It is categorised as a Read tool in the Government of Canada Open Data MCP Servers MCP Server, which means it retrieves data without modifying state.
Register the Government of Canada Open Data MCP Servers MCP server in PolicyLayer and add a rule for query_tunnels: 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 Government of Canada Open Data MCP Servers. Nothing to install.
query_tunnels 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 query_tunnels 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 query_tunnels. 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.
query_tunnels is provided by the Government of Canada Open Data MCP Servers MCP server (krunal16-c/gov-ca-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 →