get_policy_detail
View full details of a sandbox policy including effective allowlist/blocklist after merging defaults.
This record as markdown: /tools/io-github-homenshum-nodebench/get-policy-detail.md
What get_policy_detail does on Nodebench
AI agents call get_policy_detail to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_policy_detail is rated Low
This tool retrieves and displays policy configuration data (allowlist/blocklist details). While it accesses security-sensitive information that could be valuable for reconnaissance if misused by an AI agent, it performs no side effects. Severity is elevated from 'low' to 'medium' because policy details could inform attack strategies, but the read-only nature prevents it from being higher.
From the tool's definition Tool name 'get_policy_detail' and description 'View full details of a sandbox policy including effective allowlist/blocklist after merging defaults' indicates data retrieval without modification.
Attacks that exploit this kind of access
The rule that runs get_policy_detail safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_policy_detail, this is the rule to start with:
get_policy_detail 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 Nodebench, apply this rule, and every get_policy_detail call is checked against it from then on.
Questions about get_policy_detail
View full details of a sandbox policy including effective allowlist/blocklist after merging defaults. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for get_policy_detail: 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 Nodebench. Nothing to install.
get_policy_detail 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_policy_detail 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_policy_detail. 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_policy_detail is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue