transform_to_nm3 · Markdown3D MCP Server MCP: Risk & Policy

WHAT IT DOES

What transform_to_nm3 does on Markdown3D MCP Server

AI agents invoke transform_to_nm3 to trigger actions in Markdown3D MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why transform_to_nm3 needs a policy

This tool executes a non-trivial computational pipeline (semantic analysis, spatial layout calculation, XML generation) whose output depends entirely on the input markdown provided. While not destructive and not reading/writing external data, it triggers active code execution that processes user-supplied documents and generates new formatted outputs.

From the tool's definition Tool performs transformation of markdown documents into 3D visualization format (NM3), which involves processing, semantic analysis, and spatial layout operations that execute a complex algorithmic pipeline.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transform_to_nm3 Rate-limited

transform_to_nm3 stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transform_to_nm3": {
      "limits": [
        {
          "counter": "transform_to_nm3_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Markdown3D MCP Server, so you can run agents against it safely.

FAQ

Questions about transform_to_nm3

What does the transform_to_nm3 tool do? +

Transform markdown to NM3 (returns full XML - may truncate for large docs >300 nodes). It is categorised as a Execute tool in the Markdown3D MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on transform_to_nm3? +

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

What risk level is transform_to_nm3? +

transform_to_nm3 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit transform_to_nm3? +

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

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

transform_to_nm3 is provided by the Markdown3D MCP Server MCP server (mushroomfleet/markdown3d-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.