search_and_replace_in_file · Project Creator MCP

WHAT IT DOES

What search_and_replace_in_file does on Project Creator MCP

AI agents use search_and_replace_in_file to create or update resources in Project Creator MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Project Creator MCP environment.

WHY IT NEEDS A POLICY

Why search_and_replace_in_file needs a policy

The name strongly implies finding content in a file and replacing it, which is a reversible modification (Write). It could potentially be destructive if it overwrites content irreversibly, but standard search-and-replace is typically considered a write/modify operation. Confidence is reduced due to the empty description.

From the tool's definition Tool name: 'search_and_replace_in_file' — no description provided

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

search_and_replace_in_file Rate-limited

search_and_replace_in_file stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_and_replace_in_file": {
      "limits": [
        {
          "counter": "search_and_replace_in_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Project Creator MCP, so you can run agents against it safely.

FAQ

Questions about search_and_replace_in_file

What does the search_and_replace_in_file tool do? +

search_and_replace_in_file. It is categorised as a Write tool in the Project Creator MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on search_and_replace_in_file? +

Register the Project Creator MCP server in PolicyLayer and add a rule for search_and_replace_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 Project Creator MCP. Nothing to install.

What risk level is search_and_replace_in_file? +

search_and_replace_in_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit search_and_replace_in_file? +

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

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

search_and_replace_in_file is provided by the Project Creator MCP server (jackalterman/project-creator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.