List WooCommerce extensions you have access to test with QIT. Use
AI agents call list_extensions to retrieve information from QIT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays a list of accessible WooCommerce extensions for testing purposes. It performs only a read operation—querying available extensions—without creating, modifying, executing operations, or deleting data. The blast radius of misuse is minimal, as it only exposes information about which extensions are available in the testing environment.
From the tool's definition Tool name 'list_extensions' and description 'List WooCommerce extensions you have access to test with QIT' indicate a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
List WooCommerce extensions you have access to test with QIT. Use. It is categorised as a Read tool in the QIT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the QIT MCP Server MCP server in PolicyLayer and add a rule for list_extensions: 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 QIT MCP Server. Nothing to install.
list_extensions 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_extensions 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_extensions. 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_extensions is provided by the QIT MCP Server MCP server (woocommerce/qit-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 →