Low Risk

get_target_server_group

Get a specific server group in a Spinnaker cluster using a target selection strategy (e.g., newest, oldest, largest, smallest, fail). Use this when you need the most recently deployed or a specific server group without knowing its exact name. Returns JSON with the matched server group details.

Single-target operation

Part of the Spinnaker MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call get_target_server_group to retrieve information from Spinnaker without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_target_server_group only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-geiserx-spinnaker-mcp.yaml
tools:
  get_target_server_group:
    rules:
      - action: allow

See the full Spinnaker policy for all 37 tools.

Tool Name get_target_server_group
Category Read
Risk Level Low

View all 37 tools →

Agents calling read-class tools like get_target_server_group have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the get_target_server_group tool do? +

Get a specific server group in a Spinnaker cluster using a target selection strategy (e.g., newest, oldest, largest, smallest, fail). Use this when you need the most recently deployed or a specific server group without knowing its exact name. Returns JSON with the matched server group details.. It is categorised as a Read tool in the Spinnaker MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_target_server_group? +

Add a rule in your Intercept YAML policy under the tools section for get_target_server_group. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Spinnaker MCP server.

What risk level is get_target_server_group? +

get_target_server_group is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_target_server_group? +

Yes. Add a rate_limit block to the get_target_server_group rule in your Intercept 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 get_target_server_group completely? +

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

get_target_server_group is provided by the Spinnaker MCP server (spinnaker-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.