set_provider_keys · Terra Config MCP Server MCP

WHAT IT DOES

What set_provider_keys does on Terra Config MCP Server

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

This tool creates or updates provider authentication credentials in the Terra ecosystem. While not destructive (changes are reversible) or financial (no money moved), it modifies sensitive configuration data. The high severity reflects that compromised or malicious credential updates could redirect data flows, enable unauthorized integrations, or grant adversaries access to connected health/fitness data sources.

From the tool's definition Tool name 'set_provider_keys' indicates credential management. Sibling tools like 'add_custom_credentials', 'add_providers', and 'get_developer_destination_credentials' confirm this server manages authentication secrets.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_provider_keys Rate-limited

set_provider_keys 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_provider_keys": {
      "limits": [
        {
          "counter": "set_provider_keys_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_provider_keys

What does the set_provider_keys tool do? +

set_provider_keys. 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_provider_keys? +

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

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

Can I rate-limit set_provider_keys? +

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

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

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