update_module_selection

THE RISK

Medium Risk

Why update_module_selection needs a policy

This tool appears to create or modify configuration/state reversibly by narrowing module selection within the 3DCityDB session. It does not delete data irreversibly (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or merely read data (not Read).

From the tool's definition Tool name 'update_module_selection' indicates a modification operation that changes selected modules within the 3DCityDB context.

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

POLICY

How to control update_module_selection

PolicyLayer is an MCP gateway — it sits between your AI agents and 3DCityDB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_module_selection:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_module_selection": {
      "limits": [
        {
          "counter": "update_module_selection_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_module_selection 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.

Create a free account and register 3DCityDB MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More 3DCityDB MCP Server tools

Execute run_query Execute a read-only SQL SELECT query against the connected 3DCityDB database Write submit_feedback Logs feedback for a query execution (rating, errors). Read assemble_prompt Assembles the complete system prompt by orchestrating all Read get_database_schema Returns the 3DCityDB v5 table structures, column details, Read get_db_context_snapshot Returns database-level context: coordinate system, EPSG code, Read get_examples Returns SQL query examples filtered to only include examples Read get_generic_attributes Fetches generic attributes (namespace_id=3) with categorical Read get_history Returns the conversation history for a session.

All 14 3DCityDB MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_module_selection

What does the update_module_selection tool do? +

Narrows the user. It is categorised as a Write tool in the 3DCityDB 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 update_module_selection? +

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

What risk level is update_module_selection? +

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

Can I rate-limit update_module_selection? +

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

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

update_module_selection is provided by the 3DCityDB MCP Server MCP server (tum-gis/3dcitydb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every 3DCityDB MCP Server tool call.

Start from 3DCityDB MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →