import_configuration · Qontinui Web MCP Server MCP

WHAT IT DOES

What import_configuration does on Qontinui Web MCP Server

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

WHY IT NEEDS A POLICY

Why import_configuration needs a policy

Importing configurations creates or updates project data reversibly. While it modifies state (Write category), the severity is medium rather than high because: (1) the effects are typically reversible through export/reimport or deletion, (2) impact is scoped to a single project, and (3) the tool operates on configuration data rather than critical system resources.

From the tool's definition The tool is named 'import_configuration' and described as importing configuration into a project. This modifies project state by introducing new or replacement configurations, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_configuration Rate-limited

import_configuration 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_configuration": {
      "limits": [
        {
          "counter": "import_configuration_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 Qontinui Web MCP Server, so you can run agents against it safely.

FAQ

Questions about import_configuration

What does the import_configuration tool do? +

Import configuration into a project. It is categorised as a Write tool in the Qontinui Web 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_configuration? +

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

What risk level is import_configuration? +

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

Can I rate-limit import_configuration? +

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

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

import_configuration is provided by the Qontinui Web MCP Server MCP server (qontinui/qontinui-web-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.