set_destination_state · Terra Config MCP Server MCP

WHAT IT DOES

What set_destination_state does on Terra Config MCP Server

AI agents use set_destination_state 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 set_destination_state needs a policy

This tool modifies destination configuration by toggling active/inactive state, which is reversible via a subsequent call. This is Write-category behavior (state modification). Severity is medium because toggling destinations could disrupt data integrations or fitness tracking workflows, but the effect is recoverable by re-enabling the destination.

From the tool's definition Tool name 'set_destination_state' indicates modification of state. Description explicitly states it 'Set destination state (active or inactive)', changing the operational status of a destination.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_destination_state Rate-limited

set_destination_state 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": {
    "set_destination_state": {
      "limits": [
        {
          "counter": "set_destination_state_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 set_destination_state

What does the set_destination_state tool do? +

Set destination state (active or inactive). 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 set_destination_state? +

Register the Terra Config MCP Server MCP server in PolicyLayer and add a rule for set_destination_state: 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 set_destination_state? +

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

Can I rate-limit set_destination_state? +

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

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

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