check_package_installation_status

THE RISK

Low Risk

Why check_package_installation_status needs a policy

This tool retrieves status information about an existing package installation without modifying, executing, or deleting anything. It is purely informational and read-only in nature.

From the tool's definition Tool description states it 'Checks the installation status of a package' — a query operation with no side effects. Parameters are sandbox_id and package_name, both used for lookup only.

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

POLICY

How to control check_package_installation_status

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Sandbox, and nothing reaches the server without passing your rules. This is the rule we recommend for check_package_installation_status:

policy.json

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

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

Create a free account and register MCP Sandbox — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Sandbox tools

Execute execute_python_code Executes Python code in a sandbox and returns results with links to generated files. Param Execute execute_terminal_command Executes a terminal command in the specified sandbox. Parameters: sandbox_id (string), com Execute install_package_in_sandbox Installs a Python package in the specified sandbox. Parameters: sandbox_id (string), packa Write create_sandbox Creates a new Python sandbox and returns its ID for subsequent operations. Optional parame Write upload_file_to_sandbox Uploads a local file to the specified sandbox. Parameters: sandbox_id (string), local_file Read list_sandboxes Lists all existing Python sandboxes and their status. Each item also includes installed Py

All 7 MCP Sandbox tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about check_package_installation_status

What does the check_package_installation_status tool do? +

Checks the installation status of a package in a sandbox. Parameters: sandbox_id (string), package_name (string). It is categorised as a Read tool in the MCP Sandbox MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_package_installation_status? +

Register the MCP Sandbox MCP server in PolicyLayer and add a rule for check_package_installation_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 MCP Sandbox. Nothing to install.

What risk level is check_package_installation_status? +

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

Can I rate-limit check_package_installation_status? +

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

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

check_package_installation_status is provided by the MCP Sandbox MCP server (johanli233/mcp-sandbox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Sandbox tool call.

Start from MCP Sandbox, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →