Skip to main content
Glama
altrsoftware

ALTR MCP Server

Official
by altrsoftware

update_rule

Update properties of an existing masking rule (masking level, role, tag, thresholds) without deleting and recreating it.

Instructions

Update an existing masking rule's properties without deleting and recreating it.

Only the fields you provide will be updated; omitted fields remain unchanged. Use get_rules first to find the rule_id and see current values.

Masking levels reference:

  • 10000: No mask (show raw value)

  • 10001: Full mask (replace with * matching data length)

  • 10002: Email mask (show domain only)

  • 10003: Show last four

  • 10004: Constant mask (1 for numbers,

    • for strings, 1/1/2000 for dates)

  • 10005: Null (replace with NULL)

  • 10006: Full mask hash (replace with hashed value)

  • 10007: Email hash (show domain, hash local part)

  • 10008: Show last four hash (hash prefix, show last 4)

  • 10009: Constant date (replace with 12/31/9999)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
policy_idYesRaw policy ID from `get_policies`. Do not URL-encode.
rule_idYesRaw rule ID from `get_rules`. Do not URL-encode.
masking_policyNoNew masking level (10000-10009).
roleNoNew role/user group name.
tag_valueNoNew tag value for the rule.
access_rate_thresholdsNoList of access rate threshold objects, each with 'access_rate_unit' (str), 'access_rate_limit' (int), and 'action' (str).
time_window_thresholdsNoList of time window threshold objects, each with 'day' (list of str), 'start_time' (dict with hour/minute), 'end_time' (dict with hour/minute), 'timezone' (str), and 'action' (str).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries full burden. Discloses that update is partial (only provided fields) and non-destructive (no delete/recreate). Does not mention permissions or rate limits, but covers key behavioral aspects.

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

Conciseness4/5

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

Front-loaded with purpose, then usage tips, then a comprehensive but necessary mapping for masking levels. The list could be slightly trimmed but overall efficient.

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 output schema exists (return values covered), the description complements it well with preconditions, partial update behavior, and parameter reference. Adequate for the tool's complexity.

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?

Schema coverage is 100%, but description adds value by explaining the meaning of masking level codes (10000-10009), which the schema only labels. This goes beyond the schema's descriptions.

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 the resource 'existing masking rule', and distinguishes itself from siblings like delete_rule and add_rules by specifying 'without deleting and recreating it'.

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

Usage Guidelines4/5

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

Provides clear guidelines: only provided fields update, omitted fields unchanged, and advises using get_rules first to find rule_id and current values. Does not explicitly state when not to use, but context is adequate.

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/altrsoftware/altr-mcp-server'

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