import_controls · Mipiti MCP Server MCP: Risk & Policy

WHAT IT DOES

What import_controls does on Mipiti MCP Server

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

WHY IT NEEDS A POLICY

Why import_controls needs a policy

The lack of a description limits confidence, but the naming convention and context strongly suggest this tool creates or modifies control records within a security posture management system. Importing controls would be a reversible Write operation (controls can be updated, deleted, or re-imported). It does not delete data (Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial).

From the tool's definition Tool name is 'import_controls' with no description provided. Sibling tools on the server include 'add_*' operations (add_asset, add_assumption, add_evidence, etc.), all of which are Write operations that create or modify data within the Mipiti security…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_controls Rate-limited

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

FAQ

Questions about import_controls

What does the import_controls tool do? +

import_controls. It is categorised as a Write tool in the Mipiti 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 import_controls? +

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

What risk level is import_controls? +

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

Can I rate-limit import_controls? +

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

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

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