image_get_details
Ruft detaillierte Informationen zu einem Bild ab
This record as markdown: /tools/c-sakel-wp-mcp-server/image-get-details.md
What image_get_details does on WordPress MCP Server
AI agents call image_get_details 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 image_get_details is rated Low
This tool queries and returns metadata or details about an existing image in WordPress. It performs a read-only operation—no data is created, modified, deleted, or executed. The action is a straightforward information retrieval, which aligns with the 'Read' category. Low severity because misuse poses minimal risk; an agent can only view image information, not alter or delete content.
From the tool's definition Tool name 'image_get_details' and description 'Ruft detaillierte Informationen zu einem Bild ab' (Retrieves detailed information about an image) indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs image_get_details 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 image_get_details, this is the rule to start with:
image_get_details 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 image_get_details call is checked against it from then on.
Questions about image_get_details
Ruft detaillierte Informationen zu einem Bild ab. 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 image_get_details: 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.
image_get_details 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 image_get_details 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 image_get_details. 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.
image_get_details 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