AI agents call find_in_rmd to retrieve information from Ast Editor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches for substrings within R Markdown cell sources. It is a query/search operation that retrieves information without creating, modifying, or deleting data. The operation has no side effects and only reads existing content. Therefore, it falls under the Read category with low severity, as misuse would at worst reveal information but cannot cause harm to the codebase structure or functionality.
From the tool's definition "Case-sensitive substring search across all cell sources" — the tool performs a search operation that retrieves/queries data without modifying anything.
Documented attack patterns abuse exactly the kind of access find_in_rmd gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ast Editor, and nothing reaches the server without passing your rules. This is the rule we recommend for find_in_rmd:
{
"version": "1",
"default": "deny",
"tools": {
"find_in_rmd": {}
}
}find_in_rmd 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.
Case-sensitive substring search across all cell sources. It is categorised as a Read tool in the Ast Editor MCP Server, which means it retrieves data without modifying state.
Register the Ast Editor MCP server in PolicyLayer and add a rule for find_in_rmd: 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 Ast Editor. Nothing to install.
find_in_rmd 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 find_in_rmd 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 find_in_rmd. 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.
find_in_rmd is provided by the Ast Editor MCP server (kambleakash0/agent-skills). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ast Editor, 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.
59 Ast Editor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.