get_history

THE RISK

Low Risk

Why get_history needs a policy

This tool queries and retrieves existing session conversation history. It has no side effects, does not modify or delete data, and does not execute code or external operations. It is a simple read operation that falls clearly into the Read category with low severity due to minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'get_history' and description 'Returns the conversation history for a session' indicate data retrieval with no modification, deletion, or execution of operations.

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

POLICY

How to control get_history

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_history": {}
  }
}

get_history is read-only, so it stays allowed — but 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.

CAP 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). 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

All 14 3DCityDB MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_history

What does the get_history tool do? +

Returns the conversation history for a session. It is categorised as a Read tool in the 3DCityDB MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_history? +

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

get_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_history? +

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

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

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