submit_feedback

THE RISK

Medium Risk

Why submit_feedback needs a policy

This tool creates or records new feedback data, which is a reversible write operation. It has minimal blast radius since feedback logging is non-destructive and does not affect the primary database or execute arbitrary operations. Low severity because even malicious feedback cannot cause significant harm to the system or data integrity.

From the tool's definition Tool description states 'Logs feedback for a query execution (rating, errors)' - the word 'Logs' indicates data recording/creation. No deletion, financial movement, or code execution involved. The feedback mechanism creates new records in a logging system.

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

POLICY

How to control submit_feedback

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 submit_feedback:

policy.json

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

submit_feedback 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 update_module_selection Narrows the user 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 submit_feedback

What does the submit_feedback tool do? +

Logs feedback for a query execution (rating, errors). 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 submit_feedback? +

Register the 3DCityDB MCP Server MCP server in PolicyLayer and add a rule for submit_feedback: 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 submit_feedback? +

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

Can I rate-limit submit_feedback? +

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

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

submit_feedback 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 →