Read and analyze package.json file
AI agents call check_package_json to retrieve information from Build MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes data from package.json without creating, modifying, deleting, or executing anything. It is a pure read operation with no side effects. The low severity reflects minimal risk—exposure of a package.json file typically reveals only dependency metadata, versions, and project configuration already present in source control.
From the tool's definition Tool description explicitly states 'Read and analyze package.json file' with no modification or execution capabilities.
Attacks that exploit this kind of access
Read and analyze package.json file. It is categorised as a Read tool in the Build MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Build MCP Server MCP server in PolicyLayer and add a rule for check_package_json: 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 Build MCP Server. Nothing to install.
check_package_json 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 check_package_json 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 check_package_json. 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.
check_package_json is provided by the Build MCP Server MCP server (teodortrotea/mcptest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →