perf_check_images
Analysiert Bilder auf Größe, Format und Lazy-Loading
This record as markdown: /tools/c-sakel-wp-mcp-server/perf-check-images.md
What perf_check_images does on WordPress MCP Server
AI agents call perf_check_images 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 perf_check_images is rated Low
This tool performs performance analysis and auditing of image properties without modifying content, executing code, or creating side effects. It retrieves and examines metadata about images (size, format, lazy-loading status) to report findings, which is a pure Read operation. No data is changed, deleted, or executed as a result of using this tool.
From the tool's definition Tool name 'perf_check_images' and description 'Analysiert Bilder auf Größe, Format und Lazy-Loading' (Analyzes images for size, format and lazy-loading) indicate inspection/analysis only. Verbs are 'analysiert' (analyzes/checks), which is a read operation.
Attacks that exploit this kind of access
The rule that runs perf_check_images 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 perf_check_images, this is the rule to start with:
perf_check_images 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 perf_check_images call is checked against it from then on.
Questions about perf_check_images
Analysiert Bilder auf Größe, Format und Lazy-Loading. 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 perf_check_images: 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.
perf_check_images 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 perf_check_images 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 perf_check_images. 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.
perf_check_images 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