stripe_get_settings
WooCommerce Stripe Gateway settings, secrets masked, plus the active mode (live/test).
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/stripe-get-settings.md
What stripe_get_settings does on Wordpress
AI agents call stripe_get_settings to retrieve information from Wordpress without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why stripe_get_settings is rated Low
Retrieves Stripe configuration including live/test mode; masked secrets limit exposure but still sensitive.
From the tool's definition WooCommerce Stripe Gateway settings, secrets masked, retrieve mode
Attacks that exploit this kind of access
The rule that runs stripe_get_settings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stripe_get_settings, this is the rule to start with:
stripe_get_settings is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every stripe_get_settings call is checked against it from then on.
Questions about stripe_get_settings
WooCommerce Stripe Gateway settings, secrets masked, plus the active mode (live/test). It is categorised as a Read tool in the Wordpress MCP Server, which means it retrieves data without modifying state.
Register the Wordpress MCP server in PolicyLayer and add a rule for stripe_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 Wordpress. Nothing to install.
stripe_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 stripe_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 stripe_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.
stripe_get_settings is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wordpress, and thousands of servers like it.
This server
Across the catalogue