Retrieve WooCommerce settings groups
AI agents call get_settings to retrieve information from WooCommerce 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 existing settings data with no side effects. It does not create, modify, delete, or execute any operations. While settings can be sensitive (e.g., payment gateway keys), retrieval alone poses minimal risk compared to tools that modify settings or enable financial transactions. The blast radius is confined to information disclosure, which is a read-level concern.
From the tool's definition Tool name 'get_settings' and description 'Retrieve WooCommerce settings groups' indicate a read-only operation that retrieves configuration data without modification.
Attacks that exploit this kind of access
Retrieve WooCommerce settings groups. It is categorised as a Read tool in the WooCommerce MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WooCommerce MCP Server MCP server in PolicyLayer and add a rule for get_settings: 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 WooCommerce MCP Server. Nothing to install.
get_settings 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_settings 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_settings. 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_settings is provided by the WooCommerce MCP Server MCP server (lord-dubious/woocommerce-mcp-server). 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 →