Suggest contextual internal links for a post based on other published articles.
AI agents call suggest_internal_links to retrieve information from WordPress AI Content System without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads published articles and generates link suggestions. It does not modify, create, or delete any content. The actual application of links is handled by the sibling tool 'apply_internal_links', confirming this tool is purely advisory/read-only.
From the tool's definition 'Suggest contextual internal links' — the tool only suggests links based on existing published articles, implying a read/analysis operation with no side effects.
Attacks that exploit this kind of access
Suggest contextual internal links for a post based on other published articles. It is categorised as a Read tool in the WordPress AI Content System MCP Server, which means it retrieves data without modifying state.
Register the WordPress AI Content System MCP server in PolicyLayer and add a rule for suggest_internal_links: 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 AI Content System. Nothing to install.
suggest_internal_links 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 suggest_internal_links 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 suggest_internal_links. 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.
suggest_internal_links is provided by the WordPress AI Content System MCP server (ssolis-ti/wordpress_content_ai_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 →