grep_in_file

Match a JS regex against one file

Server Kontexta safiyu/kontexta
Category Read
Risk class Low
Parameters 00 required

What grep_in_file does on Kontexta

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

Why grep_in_file needs a policy

The tool performs a read-only regex search operation on a single file. It retrieves matching patterns but does not modify, execute code, delete data, or have financial impact. This is a straightforward query/search operation with minimal blast radius if misused by an AI agent.

From the tool's definition "Match a JS regex against one file" - this is a pattern-matching operation that searches within a file without modifying it. No creation, deletion, execution, or financial operations are involved.

Questions about grep_in_file

What does the grep_in_file tool do? +

Match a JS regex against one file. It is categorised as a Read tool in the Kontexta MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on grep_in_file? +

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

What risk level is grep_in_file? +

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

Can I rate-limit grep_in_file? +

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

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

grep_in_file is provided by the Kontexta MCP server (safiyu/kontexta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.