db_import · LocalWP MCP: Risk & Policy

WHAT IT DOES

What db_import does on LocalWP MCP

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

WHY IT NEEDS A POLICY

Why db_import needs a policy

An AI agent can call db_import faster than any human can review — one bad instruction and it creates or modifies resources in LocalWP MCP by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

db_import Rate-limited

db_import 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": {
    "db_import": {
      "limits": [
        {
          "counter": "db_import_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 LocalWP MCP, so you can run agents against it safely.

FAQ

Questions about db_import

What does the db_import tool do? +

Imports a SQL dump into the selected LocalWP site. You can pass either a .sql file path or a backup_site directory. Requires the. It is categorised as a Write tool in the LocalWP MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on db_import? +

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

What risk level is db_import? +

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

Can I rate-limit db_import? +

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

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

db_import is provided by the LocalWP MCP server (kazimshah39/localwp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.