Requête SQL sur les données de donnees.montreal.ca (lecture seule).
AI agents call query_montreal_sql to retrieve information from Données Québec MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite being an SQL query tool, the explicit 'read-only' constraint in the description means this tool can only retrieve data without modifying, executing code, deleting, or moving money. The most severe outcome is disclosure of queried public open data, which is a low-severity information exposure risk.
From the tool's definition Tool name 'query_montreal_sql' combined with description explicitly stating 'lecture seule' (read-only) indicates SQL queries without write/delete permissions. The description limits function to querying Montreal open data.
Attacks that exploit this kind of access
Requête SQL sur les données de donnees.montreal.ca (lecture seule). It is categorised as a Read tool in the Données Québec MCP MCP Server, which means it retrieves data without modifying state.
Register the Données Québec MCP server in PolicyLayer and add a rule for query_montreal_sql: 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 Données Québec MCP. Nothing to install.
query_montreal_sql 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_montreal_sql 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_montreal_sql. 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_montreal_sql is provided by the Données Québec MCP server (stefen-taime/donneesqc-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 →