For a given objectclass_id, walks the superclass hierarchy,
AI agents call resolve_properties to retrieve information from 3DCityDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads and resolves property definitions by traversing the class hierarchy for a given objectclass_id. This is a pure data retrieval operation with no side effects. Confidence is slightly reduced because the description is truncated and incomplete, but the described behavior is clearly read-only.
From the tool's definition 'walks the superclass hierarchy' — this is a traversal/lookup operation for a given objectclass_id to resolve properties
Documented attack patterns abuse exactly the kind of access resolve_properties gives an agent:
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 resolve_properties:
{
"version": "1",
"default": "deny",
"tools": {
"resolve_properties": {}
}
} resolve_properties is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
For a given objectclass_id, walks the superclass hierarchy,. It is categorised as a Read tool in the 3DCityDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 3DCityDB MCP Server MCP server in PolicyLayer and add a rule for resolve_properties: 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.
resolve_properties is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the resolve_properties 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.
Set action: deny in the PolicyLayer policy for resolve_properties. 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.
resolve_properties 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.
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.
Free to start. No card required.
14 3DCityDB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.