design_get_custom_css
Holt das benutzerdefinierte CSS aus dem Customizer
This record as markdown: /tools/c-sakel-wp-mcp-server/design-get-custom-css.md
What design_get_custom_css does on WordPress MCP Server
AI agents call design_get_custom_css to retrieve information from WordPress MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why design_get_custom_css is rated Low
This tool queries and retrieves existing CSS configuration data from WordPress Customizer without modifying, deleting, or executing any code. It is a read-only operation that poses minimal security risk.
From the tool's definition Tool name 'design_get_custom_css' and description 'Holt das benutzerdefinierte CSS aus dem Customizer' (retrieves custom CSS from the Customizer) indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs design_get_custom_css safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WordPress MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For design_get_custom_css, this is the rule to start with:
design_get_custom_css 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 MCP Server, apply this rule, and every design_get_custom_css call is checked against it from then on.
Questions about design_get_custom_css
Holt das benutzerdefinierte CSS aus dem Customizer. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for design_get_custom_css: 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 MCP Server. Nothing to install.
design_get_custom_css 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 design_get_custom_css 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 design_get_custom_css. 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.
design_get_custom_css is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on WordPress MCP Server, and thousands of servers like it.
This server
Across the catalogue