List all websites in the Crownpeak DQM account
AI agents call list_websites to retrieve information from Crownpeak DQM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates existing websites within an account. It has no side effects, does not modify or delete data, and does not execute external operations or move money. The blast radius of misuse is minimal — an agent could enumerate resources but cannot directly harm them. It clearly falls under the Read category.
From the tool's definition Tool name is 'list_websites' and description states it 'List all websites in the Crownpeak DQM account' — this is a retrieval/query operation with no modification of data.
Attacks that exploit this kind of access
List all websites in the Crownpeak DQM account. It is categorised as a Read tool in the Crownpeak DQM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Crownpeak DQM MCP Server MCP server in PolicyLayer and add a rule for list_websites: 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 Crownpeak DQM MCP Server. Nothing to install.
list_websites 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_websites 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_websites. 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_websites is provided by the Crownpeak DQM MCP Server MCP server (ptylr/crownpeak-dqm-node-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 →