Pages that were excluded from index — shows reasons.
AI agents call get_excluded_pages to retrieve information from SergeyKrin9/mcp Servers without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about excluded pages from a search engine index (likely Yandex.Webmaster or Google Search Console). The verb 'get' and the action of 'shows reasons' confirm it performs data retrieval only. No data is created, modified, deleted, or financial operations are involved. This is a read-only operation that would be used for monitoring and diagnostic purposes.
From the tool's definition Tool name 'get_excluded_pages' and description 'Pages that were excluded from index — shows reasons' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Pages that were excluded from index — shows reasons. It is categorised as a Read tool in the SergeyKrin9/mcp Servers MCP Server, which means it retrieves data without modifying state.
Register the SergeyKrin9/mcp Servers MCP server in PolicyLayer and add a rule for get_excluded_pages: 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 SergeyKrin9/mcp Servers. Nothing to install.
get_excluded_pages 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_excluded_pages 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_excluded_pages. 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_excluded_pages is provided by the SergeyKrin9/mcp Servers MCP server (sergeykrin9/mcp-servers). 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 →