Get SEO issues for entire site with health score. Returns health score (0-100), categorized issues by severity, and prioritized recommendations for fixes.
AI agents call get_issues to retrieve information from Rampify MCP Server 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 analysis results from Google Search Console data and site audits. It performs no side effects, creates no data modifications, executes no commands, and initiates no external operations. The output is informational analysis used for decision-making, not for actuating changes.
From the tool's definition Tool description states it 'Returns health score, categorized issues by severity, and prioritized recommendations' — pure data retrieval with no modification, deletion, or execution of external operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get SEO issues for entire site with health score. Returns health score (0-100), categorized issues by severity, and prioritized recommendations for fixes. It is categorised as a Read tool in the Rampify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rampify MCP Server MCP server in PolicyLayer and add a rule for get_issues: 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 Rampify MCP Server. Nothing to install.
get_issues 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 get_issues 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 get_issues. 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.
get_issues is provided by the Rampify MCP Server MCP server (rampify-dev/rampify-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 →