Fetch a paginated list of prompts where the specified brand is mentioned in LLM results. Maps to /v1/ai-search/prompts-by-brand.
AI agents call aiSearchPromptsByBrand to retrieve information from Seo Data Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves SEO/brand analysis data without creating, modifying, deleting, executing code, or moving money. It is purely informational—typical of Read category tools used for competitive research and monitoring.
From the tool's definition Tool name includes 'Fetch' and 'list' in description; maps to a GET endpoint (/v1/ai-search/prompts-by-brand) that retrieves existing data about brand mentions in LLM results without modifying anything.
Attacks that exploit this kind of access
Fetch a paginated list of prompts where the specified brand is mentioned in LLM results. Maps to /v1/ai-search/prompts-by-brand. It is categorised as a Read tool in the Seo Data Api MCP Server, which means it retrieves data without modifying state.
Register the Seo Data Api MCP server in PolicyLayer and add a rule for aiSearchPromptsByBrand: 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 Seo Data Api. Nothing to install.
aiSearchPromptsByBrand 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 aiSearchPromptsByBrand 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 aiSearchPromptsByBrand. 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.
aiSearchPromptsByBrand is provided by the Seo Data Api MCP server (teake1404/seo-data-api-mcp-server). 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 →