List every Search Console property the authenticated
AI agents call search_console_sites_list to retrieve information from Mureo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists data (Search Console properties) belonging to the authenticated user. It performs no modifications, deletions, code execution, or financial transactions. The blast radius of misuse is limited to information disclosure of which Search Console properties exist, which is a read-only operation.
From the tool's definition Tool name is 'search_console_sites_list' and description indicates it 'List[s] every Search Console property' — a pure enumeration/query operation with no side effects.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access search_console_sites_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mureo, and nothing reaches the server without passing your rules. This is the rule we recommend for search_console_sites_list:
{
"version": "1",
"default": "deny",
"tools": {
"search_console_sites_list": {}
}
}search_console_sites_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List every Search Console property the authenticated. It is categorised as a Read tool in the Mureo MCP Server, which means it retrieves data without modifying state.
Register the Mureo MCP server in PolicyLayer and add a rule for search_console_sites_list: 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 Mureo. Nothing to install.
search_console_sites_list 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 search_console_sites_list 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 search_console_sites_list. 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.
search_console_sites_list is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mureo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
185 Mureo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.