Get the function that contains a specific line number.
AI agents call get_function_at_line to retrieve information from MCP File Edit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs code analysis by retrieving structural information about functions at specified line numbers. It has no side effects, does not execute code, does not modify files, and does not delete data. It is purely informational and falls clearly into the Read category. Severity is low because misuse only exposes existing code structure information without enabling harmful actions.
From the tool's definition Tool name is 'get_function_at_line' and description states it retrieves ('Get') the function containing a specific line number. This is a read-only query operation that extracts code metadata without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access get_function_at_line gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP File Edit, and nothing reaches the server without passing your rules. This is the rule we recommend for get_function_at_line:
{
"version": "1",
"default": "deny",
"tools": {
"get_function_at_line": {}
}
}get_function_at_line 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.
Get the function that contains a specific line number. It is categorised as a Read tool in the MCP File Edit MCP Server, which means it retrieves data without modifying state.
Register the MCP File Edit MCP server in PolicyLayer and add a rule for get_function_at_line: 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 MCP File Edit. Nothing to install.
get_function_at_line 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 get_function_at_line 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 get_function_at_line. 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.
get_function_at_line is provided by the MCP File Edit MCP server (patrickomatik/mcp-file-edit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP File Edit, 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.
32 MCP File Edit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.