Low Risk

package_file_grep

Search a single file from a package for lines matching a JavaScript regular expression. Pass the

How to control package_file_grep ↓

AI agents call package_file_grep to retrieve information from Socket MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool performs a search/grep operation on package file contents using regex, which is a query operation that retrieves matching lines without altering data. It has no side effects, no code execution capabilities, and no destructive potential. It fits squarely in the Read category with low severity since it only inspects existing file contents.

From the tool's definition Tool description: 'Search a single file from a package for lines matching a JavaScript regular expression.' The verb 'search' and the read-only nature of pattern matching on file contents indicate retrieval without modification.

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "package_file_grep": {}
  }
}

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

  1. Create a free account and register Socket MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the package_file_grep tool do? +

Search a single file from a package for lines matching a JavaScript regular expression. Pass the. It is categorised as a Read tool in the Socket MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on package_file_grep? +

Register the Socket MCP Server MCP server in PolicyLayer and add a rule for package_file_grep: 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 Socket MCP Server. Nothing to install.

What risk level is package_file_grep? +

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

Can I rate-limit package_file_grep? +

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

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

package_file_grep is provided by the Socket MCP Server MCP server (socketdev/socket-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Socket MCP Server tool call.

Deterministic rules across all 7 Socket MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

7 Socket MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.