AI agents call seoagent_domain_reputation_history to retrieve information from Seoagent 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 historical domain reputation metrics. It performs a passive lookup operation that reads existing data without creating, modifying, deleting, or executing any actions. The blast radius if misused is minimal — an agent could only retrieve reputation history data, which poses no destructive or operational risk.
From the tool's definition Tool name includes 'history' and description states 'Track domain reputation (DR) changes over time' — indicates retrieval and monitoring of historical data with no modification or deletion of records.
Attacks that exploit this kind of access
Track domain reputation (DR) changes over time. It is categorised as a Read tool in the Seoagent MCP Server, which means it retrieves data without modifying state.
Register the Seoagent MCP server in PolicyLayer and add a rule for seoagent_domain_reputation_history: 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 Seoagent. Nothing to install.
seoagent_domain_reputation_history 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 seoagent_domain_reputation_history 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 seoagent_domain_reputation_history. 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.
seoagent_domain_reputation_history is provided by the Seoagent MCP server (yagomp/seoagent). 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 →