Skip to main content
Glama
Sign In
@argosvix/mcp-server

@argosvix/mcp-server

by argosvix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_policy_gate

Update a runtime policy gate to modify model allowlist, block PII or secrets, set enforcement mode, and toggle enabled status.

Instructions

Update a runtime policy gate (Pro+ only). Partially updates modelAllowlist (null clears the restriction) / blockPii / blockSecrets / enforceMode / enabled. Example phrasing: "add gpt-4o-mini to the allowlist" / "enable secret blocking"

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "policyId": "<policyId>"
    },
    "name": "update_policy_gate"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNo
blockPiiNo
policyIdYesTarget policy id (from get_policy_gate, starts with pg_)
enforceModeNo
blockSecretsNo
modelAllowlistNoNew allowlist (null clears the model restriction)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.30.0-alpha.14

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses 'Partially updates' and that null clears the restriction for modelAllowlist. However, it does not mention permissions, idempotency, return value, or side effects, limiting transparency.

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?

The description is two sentences plus examples, front-loaded with purpose and scope, and contains no fluff. Every part adds value.

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

Completeness3/5

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

The description covers fields and gives usage examples but lacks details on return value, prerequisites, or implications of settings (e.g., enforceMode). For a mutation tool with no output schema or annotations, more context would be beneficial.

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 33% schema description coverage, the description adds value by listing all modifiable fields and explaining the null behavior for modelAllowlist. It does not provide detailed semantics for other fields, but compensates for the low schema coverage.

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 clearly states the verb 'Update' and resource 'runtime policy gate', lists the modifiable fields, and provides examples. This distinguishes it from siblings like create, delete, and get.

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

Usage Guidelines3/5

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

The description mentions 'Pro+ only' as a licensing restriction but does not explicitly state when not to use this tool or alternatives like create_policy_gate. Examples give usage context, but no exclusion criteria.

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

Deploy Server

Other Tools