list_tools_with_examples
AI agents call list_tools_with_examples 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.
This tool appears to enumerate available tools and their example usage, which is introspective and read-only. It retrieves metadata about tools themselves rather than modifying, executing external operations, or deleting data. The confidence is slightly reduced due to the empty description, but the naming convention and context strongly suggest a non-destructive listing operation.
From the tool's definition Tool name 'list_tools_with_examples' indicates a listing/enumeration operation. The description is empty, providing no additional context, but the name structure follows a read pattern (list, get, describe, find) consistent with sibling tools like…
Attacks that exploit this kind of access
list_tools_with_examples. 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 list_tools_with_examples: 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.
list_tools_with_examples 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_tools_with_examples 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_tools_with_examples. 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_tools_with_examples 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 →