configure_key · Model Radar MCP: Risk & Policy

WHAT IT DOES

What configure_key does on Model Radar

AI agents use configure_key to create or update resources in Model Radar — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Model Radar environment.

WHY IT NEEDS A POLICY

Why configure_key needs a policy

The tool appears to create or modify configuration state (Write category). Severity is medium because misconfiguration could disrupt service or expose credentials, but without a description, the exact blast radius is unclear.

From the tool's definition Tool name 'configure_key' suggests setting or modifying a configuration key, likely related to API keys or authentication credentials for the 130+ LLM models this server manages.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

configure_key Rate-limited

configure_key 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": {
    "configure_key": {
      "limits": [
        {
          "counter": "configure_key_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 Model Radar, so you can run agents against it safely.

FAQ

Questions about configure_key

What does the configure_key tool do? +

configure_key. It is categorised as a Write tool in the Model Radar MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on configure_key? +

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

What risk level is configure_key? +

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

Can I rate-limit configure_key? +

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

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

configure_key is provided by the Model Radar MCP server (srclight/model-radar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.