get_package_details
Fetch detailed package information from the s&box asset library (asset.party) including title, author, version, downloads, ratings, and dependencies
This record as markdown: /tools/sbox/get-package-details.md
What get_package_details does on Sbox
AI agents call get_package_details to retrieve information from Sbox without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_package_details is rated Low
This tool retrieves metadata from an external package repository (asset.party) without modifying, creating, or deleting anything. The operations are pure queries that return public asset information. There is no capability to execute code, modify packages, or cause destructive changes. The blast radius of misuse is minimal—worst case an agent could gather information about game packages, which poses no security risk.
From the tool's definition Tool name contains 'get_' and description explicitly states 'Fetch detailed package information' with read-only operations: retrieving title, author, version, downloads, ratings, and dependencies from an asset library with no side effects.
Attacks that exploit this kind of access
The rule that runs get_package_details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_package_details, this is the rule to start with:
get_package_details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sbox, apply this rule, and every get_package_details call is checked against it from then on.
Questions about get_package_details
Fetch detailed package information from the s&box asset library (asset.party) including title, author, version, downloads, ratings, and dependencies. It is categorised as a Read tool in the Sbox MCP Server, which means it retrieves data without modifying state.
Register the Sbox MCP server in PolicyLayer and add a rule for get_package_details: 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 Sbox. Nothing to install.
get_package_details 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 get_package_details 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 get_package_details. 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.
get_package_details is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sbox, and thousands of servers like it.
This server
Across the catalogue