AI agents invoke generate_keywords to trigger actions in Outrank. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation (queuing keyword research) rather than simply reading existing data or writing a stored record. 'Queue' implies dispatching a background job or external process whose effects depend on the arguments provided. It is not purely destructive or financial, but it does execute an operation with side effects beyond a simple data write.
From the tool's definition Queue keyword cluster research for a product on a broad topic
Attacks that exploit this kind of access
Queue keyword cluster research for a product on a broad topic. It is categorised as a Execute tool in the Outrank MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Outrank MCP server in PolicyLayer and add a rule for generate_keywords: 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 Outrank. Nothing to install.
generate_keywords is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the generate_keywords 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 generate_keywords. 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.
generate_keywords is provided by the Outrank MCP server (nobanks/outrank-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 →