add_developer_destination · Terra Config MCP Server MCP

WHAT IT DOES

What add_developer_destination does on Terra Config MCP Server

AI agents use add_developer_destination to create or update resources in Terra Config MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Terra Config MCP Server environment.

WHY IT NEEDS A POLICY

Why add_developer_destination needs a policy

This tool creates new destination configurations in the TerraAPI dashboard, which are reversible write operations. It lacks the characteristics of Execute (no arbitrary code/commands), Destructive (not irreversible), Financial (no money movement), or Read (modifies rather than retrieves).

From the tool's definition Tool name 'add_developer_destination' indicates creation of a new destination configuration. The server manages 'destinations' which are data routing endpoints in the Terra ecosystem.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_developer_destination Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about add_developer_destination

What does the add_developer_destination tool do? +

add_developer_destination. It is categorised as a Write tool in the Terra Config 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 add_developer_destination? +

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

What risk level is add_developer_destination? +

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

Can I rate-limit add_developer_destination? +

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

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

add_developer_destination is provided by the Terra Config MCP Server MCP server (tryterra/terramcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.