Low Risk

find_large_functions

Find functions exceeding a line count threshold. Args: threshold: Minimum lines to flag (default 50). limit: Maximum results (default 20).

How to control find_large_functions ↓

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

Low Risk

This tool searches and retrieves information about code structure (functions by size) without creating, modifying, deleting, or executing anything. It is a pure read operation on code metadata/analysis. The low severity reflects minimal blast radius—misuse would return unwanted query results but cause no side effects or damage.

From the tool's definition Tool name 'find_large_functions' and description indicate retrieval/query operations: 'Find functions exceeding a line count threshold' with parameters for filtering (threshold, limit) and returning results.

Documented attack patterns abuse exactly the kind of access find_large_functions gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Qualixar/superlocalmemory, and nothing reaches the server without passing your rules. This is the rule we recommend for find_large_functions:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_large_functions": {}
  }
}

find_large_functions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Qualixar/superlocalmemory — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the find_large_functions tool do? +

Find functions exceeding a line count threshold. Args: threshold: Minimum lines to flag (default 50). limit: Maximum results (default 20). It is categorised as a Read tool in the Qualixar/superlocalmemory MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_large_functions? +

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

What risk level is find_large_functions? +

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

Can I rate-limit find_large_functions? +

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

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

find_large_functions is provided by the Qualixar/superlocalmemory MCP server (qualixar/superlocalmemory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Qualixar/superlocalmemory tool call.

Deterministic rules across all 59 Qualixar/superlocalmemory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

59 Qualixar/superlocalmemory tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.