Return all sites verified in Yandex.Webmaster for the current user.
AI agents call list_hosts 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 performs a read-only query to enumerate sites/hosts in a Webmaster account. It retrieves data (list of verified sites) without creating, modifying, deleting, or executing any operations. The blast radius is low as it only exposes information about already-verified properties that the authenticated user owns, though care should be taken not to leak this metadata to unauthorized parties.
From the tool's definition Tool name 'list_hosts' and description 'Return all sites verified in Yandex.Webmaster' indicates a retrieval operation that queries existing data without modification or side effects.
Attacks that exploit this kind of access
Return all sites verified in Yandex.Webmaster for the current user. 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 list_hosts: 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.
list_hosts 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 list_hosts 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 list_hosts. 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.
list_hosts 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 →