setup_guide · Model Radar MCP: Risk & Policy

WHAT IT DOES

What setup_guide does on Model Radar

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

An AI agent can call setup_guide faster than any human can review — one bad instruction and it creates or modifies resources in Model Radar by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_guide Rate-limited

setup_guide 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": {
    "setup_guide": {
      "limits": [
        {
          "counter": "setup_guide_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 setup_guide

What does the setup_guide tool do? +

setup_guide. 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 setup_guide? +

Register the Model Radar MCP server in PolicyLayer and add a rule for setup_guide: 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 setup_guide? +

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

Can I rate-limit setup_guide? +

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

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

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