Read .expanse.json with optional JSON Pointer path
AI agents call desktop_read_json 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 queries/retrieves configuration data from a JSON file. It performs a read-only operation without creating, modifying, deleting, or executing anything. The optional JSON Pointer parameter allows filtering what is read but does not alter the underlying data. This is a straightforward data retrieval pattern with minimal risk.
From the tool's definition Tool name contains 'read' and description states 'Read .expanse.json with optional JSON Pointer path' — explicitly a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access desktop_read_json 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_read_json:
{
"version": "1",
"default": "deny",
"tools": {
"desktop_read_json": {}
}
}desktop_read_json 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.
Read .expanse.json with optional JSON Pointer path. 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_read_json: 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_read_json 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_read_json 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_read_json. 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_read_json 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.