Check which style preset is currently active
AI agents call get_active_preset to retrieve information from Noleemits Vision Builder MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about the currently active style preset in the WordPress/Elementor environment. It performs no data modification, does not execute external commands, and has no destructive or financial implications. It is a simple read/query operation with minimal blast radius if misused by an agent—at worst, an agent could learn what preset is active, which poses no security risk.
From the tool's definition Tool name 'get_active_preset' and description 'Check which style preset is currently active' indicate a query operation that retrieves current state without modification or side effects.
Attacks that exploit this kind of access
Check which style preset is currently active. It is categorised as a Read tool in the Noleemits Vision Builder MCP MCP Server, which means it retrieves data without modifying state.
Register the Noleemits Vision Builder MCP server in PolicyLayer and add a rule for get_active_preset: 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 Noleemits Vision Builder MCP. Nothing to install.
get_active_preset 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_active_preset 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_active_preset. 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_active_preset is provided by the Noleemits Vision Builder MCP server (noleemits/vision-builder-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 →