AI agents call js_search to retrieve information from Burp Mcp Plus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a search/query operation that retrieves data from existing JavaScript files without executing code, modifying files, or triggering external operations. The verb 'grep' indicates pattern matching and retrieval only. Even though the server integrates with Burp Suite (a security testing tool), this particular tool is limited to non-destructive data retrieval.
From the tool's definition Tool performs grep/search across JS files: 'Grep across all on-disk JS files in a source' — a read-only query operation with no modification or execution capabilities.
Documented attack patterns abuse exactly the kind of access js_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Burp Mcp Plus, and nothing reaches the server without passing your rules. This is the rule we recommend for js_search:
{
"version": "1",
"default": "deny",
"tools": {
"js_search": {}
}
}js_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Grep across all on-disk JS files in a source. It is categorised as a Read tool in the Burp Mcp Plus MCP Server, which means it retrieves data without modifying state.
Register the Burp Mcp Plus MCP server in PolicyLayer and add a rule for js_search: 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 Burp Mcp Plus. Nothing to install.
js_search 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 js_search 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 js_search. 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.
js_search is provided by the Burp Mcp Plus MCP server (titaniumtushar/burp-mcp-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Burp Mcp Plus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Burp Mcp Plus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.