get_node_package_scripts
Get Node package scripts (XPack)
This record as markdown: /tools/eaveluo-1panel-mcp/get-node-package-scripts.md
What get_node_package_scripts does on 1Panel MCP Server
AI agents call get_node_package_scripts to retrieve information from 1Panel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_node_package_scripts is rated Low
This tool retrieves and lists Node.js package scripts, which is a read-only query operation with no side effects. It does not execute scripts, modify files, delete data, or perform financial operations. The blast radius of misuse is minimal—an attacker could only discover what scripts are available, not execute them or cause infrastructure damage. The low severity reflects the informational nature of the operation.
From the tool's definition Tool name 'get_node_package_scripts' and description 'Get Node package scripts (XPack)' indicate a retrieval operation that reads package.json or similar metadata to list available npm scripts without modifying them.
Attacks that exploit this kind of access
The rule that runs get_node_package_scripts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1Panel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_node_package_scripts, this is the rule to start with:
get_node_package_scripts 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 1Panel MCP Server, apply this rule, and every get_node_package_scripts call is checked against it from then on.
Questions about get_node_package_scripts
Get Node package scripts (XPack). It is categorised as a Read tool in the 1Panel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 1Panel MCP Server MCP server in PolicyLayer and add a rule for get_node_package_scripts: 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 1Panel MCP Server. Nothing to install.
get_node_package_scripts 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_node_package_scripts 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_node_package_scripts. 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_node_package_scripts is provided by the 1Panel MCP Server MCP server (eaveluo/1panel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1Panel MCP Server, and thousands of servers like it.
This server
Across the catalogue