app_inspect

Inspect a .0n application bundle without passphrase. Shows metadata, endpoints, workflows, and automations. Example: app_inspect({ bundle:

SERVER0nmcp SOURCE0nmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-0nork-0nmcp/app-inspect.md

WHAT IT DOES

What app_inspect does on 0nmcp

AI agents call app_inspect to retrieve information from 0nmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why app_inspect is rated Low

The tool reads and displays information about application bundles (metadata, endpoints, workflows, automations) without executing code, modifying data, or requiring authentication (operates 'without passphrase'). This is fundamentally a Read operation.

From the tool's definition Tool description states 'Inspect a .0n application bundle' and 'Shows metadata, endpoints, workflows, and automations' — these are retrieval/query operations with no modification or execution mentioned.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs app_inspect safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For app_inspect, this is the rule to start with:

app_inspect Allowed

app_inspect is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "app_inspect": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 0nmcp, apply this rule, and every app_inspect call is checked against it from then on.

FAQ

Questions about app_inspect

What does the app_inspect tool do? +

Inspect a .0n application bundle without passphrase. Shows metadata, endpoints, workflows, and automations. Example: app_inspect({ bundle:. It is categorised as a Read tool in the 0nmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on app_inspect? +

Register the 0n MCP server in PolicyLayer and add a rule for app_inspect: 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 0nmcp. Nothing to install.

What risk level is app_inspect? +

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

Can I rate-limit app_inspect? +

Yes. Add a rate_limit block to the app_inspect 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 app_inspect completely? +

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

app_inspect is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 0n, and thousands of servers like it.

This server

All 218 0n tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →