This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/wordpress-get-post.md
What wordpress_get_post does on UnClick
AI agents call wordpress_get_post to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
post_id | string | Yes | Post id |
site_url | string | Yes | WordPress site URL |
username | string | Yes | WordPress username |
app_password | string | Yes | WordPress application password |
Parameters from the server's own tool schema.
Why wordpress_get_post is rated Low
This tool retrieves a single WordPress post based on a provided ID. It is a read-only operation that queries and returns data without side effects, modifications, or destructive actions. The operation is straightforward data retrieval, making it a Read category tool with low severity since misuse would only expose existing published content.
From the tool's definition Tool name 'wordpress_get_post' and description 'Get a single WordPress post by id' indicate retrieval of existing data with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
The rule that runs wordpress_get_post safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wordpress_get_post, this is the rule to start with:
wordpress_get_post 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 UnClick, apply this rule, and every wordpress_get_post call is checked against it from then on.
Questions about wordpress_get_post
Get a single WordPress post by id. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
wordpress_get_post accepts 4 parameters: post_id, site_url, username, app_password. Required: post_id, site_url, username, app_password. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for wordpress_get_post: 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 UnClick. Nothing to install.
wordpress_get_post 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 wordpress_get_post 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 wordpress_get_post. 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.
wordpress_get_post is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue