Skip to main content
Glama
logic-arts-official

scaleway-ops-mcp-server

Set rules on a Scaleway IAM Policy

scaleway_iam_set_policy_rules
DestructiveIdempotent

Atomically overwrite all rules on an existing policy to add or remove permission sets safely. Never get locked out: list current rules first, then replace the entire array.

Instructions

Overwrite the COMPLETE rules array on an existing Policy in one atomic call - the safe way to add or remove a permission set on a live policy. Prefer this over delete+recreate: deleting a policy that grants its own holder IAMPolicyManager revokes that permission the instant it's deleted, before a replacement can be created, which can lock the credential you're using out of IAM entirely. Call scaleway_iam_list_policy_rules first to get the current array before changing it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rulesYesThe COMPLETE rules array to set - this REPLACES every existing rule on the policy, it does not merge or append. Call scaleway_iam_list_policy_rules first, add/remove/edit within that array, then pass the whole thing back here. This is the safe way to change a live policy's grants: unlike delete+recreate, there's no window where the policy (or the permissions it grants its own holder) doesn't exist.
policy_idYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond annotations (destructiveHint=true, idempotentHint=true), the description explains the destructive nature (overwrites complete array, not merge), atomicity, and the safety rationale. It warns about the IAMPolicyManager lockout scenario, adding context about credential risk that annotations do not cover. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences front-loaded with the core purpose and safety proposition. Every sentence earns its place: purpose, danger of alternative, prerequisite action. No redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity and sensitivity of IAM policy rules modification, the description covers the core behavior, atomic safety, lockout risk, prerequisite call, and the intended use case (add/remove permission sets). It is complete enough for an agent to correctly select and invoke the tool, especially with the sibling context and annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at 50% (policy_id lacks a description), the description compensates by thoroughly explaining the rules parameter's behavior and usage workflow (call list first, pass entire array). It does not add meaning for policy_id but heavily enriches the main parameter's semantics beyond the schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description immediately states the verb 'Overwrite' and resource 'COMPLETE rules array on an existing Policy', explicitly distinguishing itself from the delete+recreate pattern. It clearly specifies the atomic nature and safety, differentiating from sibling operations like scaleway_iam_list_policy_rules (read-only) or scaleway_iam_delete_policy (whole policy deletion).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance: 'the safe way to add or remove a permission set on a live policy' and 'Prefer this over delete+recreate' with a detailed explanation of the lockout danger. It also instructs to call scaleway_iam_list_policy_rules first, providing a clear prerequisite workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logic-arts-official/scaleway-ops-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server