Skip to main content
Glama
enkryptai

Enkrypt AI MCP Server

Official
by enkryptai

update_guardrails_policy

Modify and enhance guardrails policies by updating detector configurations, including injection attacks, PII, toxicity, and bias, ensuring robust AI safety and compliance.

Instructions

Update an existing guardrails policy with new configuration.

Args: policy_name: The name of the policy to update. detectors: Dictionary of detector configurations. Each key should be the name of a detector, and the value should be a dictionary of settings for that detector. Available detectors and their configurations are as follows:

                  - injection_attack: Configured using InjectionAttackDetector model. Example: {"enabled": True}
                  - pii: Configured using PiiDetector model. Example: {"enabled": False, "entities": ["email", "phone"]}
                  - nsfw: Configured using NsfwDetector model. Example: {"enabled": True}
                  - toxicity: Configured using ToxicityDetector model. Example: {"enabled": True}
                  - topic: Configured using TopicDetector model. Example: {"enabled": True, "topic": ["politics", "religion"]}
                  - keyword: Configured using KeywordDetector model. Example: {"enabled": True, "banned_keywords": ["banned_word1", "banned_word2"]}
                  - policy_violation: Configured using PolicyViolationDetector model. Example: {"enabled": True, "need_explanation": True, "policy_text": "Your policy text here"}
                  - bias: Configured using BiasDetector model. Example: {"enabled": True}
                  - copyright_ip: Configured using CopyrightIpDetector model. Example: {"enabled": True}
                  - system_prompt: Configured using SystemPromptDetector model. Example: {"enabled": True, "index": "system_prompt_index"}
                  
                  Example usage: 
                  {
                      "injection_attack": {"enabled": True}, 
                      "nsfw": {"enabled": True}
                  }

Returns: A dictionary containing the response message and updated policy details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
detectorsYes
policy_descriptionNoUpdated policy configuration
policy_nameYes
Behavior2/5

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

With no annotations provided, the description carries full burden but offers limited behavioral insight. It implies a mutation operation ('update') but doesn't disclose permissions needed, whether changes are reversible, rate limits, or error handling. The return format is vaguely described as 'dictionary containing response message and updated policy details', lacking specifics on structure or success/failure indicators.

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

Conciseness3/5

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

The description is front-loaded with the core purpose but becomes lengthy with detailed detector examples. While informative, the extensive listing of detectors could be more concise. Structure is logical with Args and Returns sections, but some redundancy in examples slightly reduces efficiency.

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?

Given 3 parameters, nested objects, no annotations, and no output schema, the description is partially complete. It excels in parameter semantics but lacks behavioral context, usage guidelines, and detailed return value explanation. For a mutation tool with complexity, it should cover more aspects like error cases or side effects to be fully adequate.

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

Parameters5/5

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

Schema description coverage is 0%, so the description compensates fully. It details 'policy_name' as the target policy and 'detectors' as a dictionary with specific detector configurations, including examples for each detector type (e.g., injection_attack, pii) and a usage example. This adds significant meaning beyond the bare schema, clarifying parameter purposes and formats effectively.

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

Purpose4/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 'existing guardrails policy with new configuration', making the purpose unambiguous. It distinguishes from siblings like 'add_guardrails_policy' (create vs update) and 'remove_guardrails_policy' (modify vs delete), though not explicitly named. The specificity is good but lacks explicit sibling differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'add_guardrails_policy' for creation or 'modify_deployment_config' for related changes. It mentions updating an existing policy but doesn't specify prerequisites (e.g., policy must exist) or contextual constraints, leaving usage unclear relative to siblings.

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

Related 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/enkryptai/enkryptai-mcp-server'

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