List all custom components in the project
AI agents call desktop_list_components to retrieve information from 8th Wall MCP Server 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 operation—listing components—which has no side effects. It retrieves information about the current state of a project but does not create, modify, execute, or delete any data. The blast radius is minimal: an agent cannot cause harm by listing components.
From the tool's definition Tool name 'desktop_list_components' and description 'List all custom components in the project' indicate a retrieval operation that queries existing project components without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access desktop_list_components gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 8th Wall MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for desktop_list_components:
{
"version": "1",
"default": "deny",
"tools": {
"desktop_list_components": {}
}
}desktop_list_components 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 all custom components in the project. It is categorised as a Read tool in the 8th Wall MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 8th Wall MCP Server MCP server in PolicyLayer and add a rule for desktop_list_components: 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 8th Wall MCP Server. Nothing to install.
desktop_list_components 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 desktop_list_components 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 desktop_list_components. 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.
desktop_list_components is provided by the 8th Wall MCP Server MCP server (superdwayne/8thwallmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from 8th Wall MCP Server, 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.
64 8th Wall MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.