generate_function_imports · FDEP MCP Server MCP

WHAT IT DOES

What generate_function_imports does on FDEP MCP Server

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

WHY IT NEEDS A POLICY

Why generate_function_imports needs a policy

This tool generates (creates/produces) import statements for code elements. While import statement generation is reversible and doesn't delete data, it modifies source code by adding or suggesting import directives. This is a Write operation rather than Read because it produces new code artifacts rather than merely retrieving or analyzing existing code.

From the tool's definition Tool name 'generate_function_imports' and description 'Generate all necessary import statements for a function or code element' indicates creation/modification of import statements, which are code artifacts.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_function_imports Rate-limited

generate_function_imports 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": {
    "generate_function_imports": {
      "limits": [
        {
          "counter": "generate_function_imports_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 FDEP MCP Server, so you can run agents against it safely.

FAQ

Questions about generate_function_imports

What does the generate_function_imports tool do? +

Generate all necessary import statements for a function or code element. It is categorised as a Write tool in the FDEP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_function_imports? +

Register the FDEP MCP Server MCP server in PolicyLayer and add a rule for generate_function_imports: 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 FDEP MCP Server. Nothing to install.

What risk level is generate_function_imports? +

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

Can I rate-limit generate_function_imports? +

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

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

generate_function_imports is provided by the FDEP MCP Server MCP server (juspay/fdep-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.