Low Risk

assets_status

Report availability of PolyHaven integration

How to control assets_status ↓

What assets_status does on 8th Wall MCP Server

AI agents call assets_status 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.

Low Risk

Why assets_status needs a policy

This tool retrieves the status/availability state of an external asset integration (PolyHaven). It queries information without creating, modifying, deleting, executing code, or causing financial impacts. This is a straightforward read operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool named 'assets_status' with description 'Report availability of PolyHaven integration' — the word 'report' and 'availability' indicate status checking or querying without modification.

Documented attack patterns abuse exactly the kind of access assets_status gives an agent:

How to control assets_status

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 assets_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "assets_status": {}
  }
}

assets_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register 8th Wall MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about assets_status

What does the assets_status tool do? +

Report availability of PolyHaven integration. It is categorised as a Read tool in the 8th Wall MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on assets_status? +

Register the 8th Wall MCP Server MCP server in PolicyLayer and add a rule for assets_status: 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.

What risk level is assets_status? +

assets_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit assets_status? +

Yes. Add a rate_limit block to the assets_status 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.

How do I block assets_status completely? +

Set action: deny in the PolicyLayer policy for assets_status. 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.

What MCP server provides assets_status? +

assets_status 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.

Enforce policy on every 8th Wall MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.