Skip to main content
Glama
iracic82

infoblox-ddi-mcp

by iracic82

manage_security_policy

Destructive

Manage DNS security resources like policies, named lists, app filters, internal domains, access codes, and category filters. Create, update, list, or delete them.

Instructions

Manage DNS security resources: policies (read-only), named lists, application filters, internal domains, access codes, and category filters. USE THIS for security policy CRUD. For posture assessment use assess_security_posture(). For threat investigation use investigate_threat().

NOTE: Security policies are read-only via API (list/get only). Named lists support full CRUD + partial item updates. Category filters use full replace (PUT) for updates — both name and categories are required.

Args: resource_type: Type of security resource to manage action: Operation to perform. "add_items" and "remove_items" are for named_list only — they add/remove domains from an existing list without replacing the entire list. name: Resource name resource_id: Resource ID for get/update/delete/add_items/remove_items items: List of domains/IPs for named lists or internal domain lists. For "add_items": items to add. For "remove_items": items to remove. categories: List of content category names — for category_filter create/update description: Description text list_type: Named list type (e.g., "custom_list") — for named_list create criteria: Application filter criteria — for app_filter create activation: Access code activation date (ISO 8601) — for access_code create expiration: Access code expiration date (ISO 8601) — for access_code create rules: Access code rules — for access_code create dry_run: If True (default), delete shows resource only. Set False to execute.

Returns: Security resource operation result

Examples: - manage_security_policy(resource_type="policy", action="list") → all security policies - manage_security_policy(resource_type="named_list", action="list") - manage_security_policy(resource_type="named_list", action="create", name="block-list", list_type="custom_list", items=["bad.com"]) - manage_security_policy(resource_type="named_list", action="update", resource_id="...", items=["bad.com", "evil.com"]) - manage_security_policy(resource_type="named_list", action="add_items", resource_id="...", items=["new-bad.com"]) - manage_security_policy(resource_type="named_list", action="remove_items", resource_id="...", items=["old-entry.com"]) - manage_security_policy(resource_type="category_filter", action="list") → all category filters - manage_security_policy(resource_type="category_filter", action="create", name="block-adult", categories=["Adult Content"]) - manage_security_policy(resource_type="category_filter", action="update", resource_id="123", name="block-adult", categories=["Adult Content", "Malware"]) - manage_security_policy(resource_type="internal_domains", action="create", name="corp-domains", items=["corp.local"])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
itemsNo
rulesNo
actionYes
dry_runNo
criteriaNo
list_typeNo
activationNo
categoriesNo
expirationNo
descriptionNo
resource_idNo
resource_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Beyond destructiveHint, the description discloses the dry_run default for delete, read-only policy access, named_list add/remove semantics (without full replacement), and category filter full-replace behavior. These details are crucial for safe invocation and are not present in 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?

The description is well-structured with clear sections (overview, usage notes, args, returns, examples). Every sentence adds operational value; the examples illustrate complex combinations without redundancy.

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 tool's complexity (8 resource types, 7 actions, 13 parameters), the description comprehensively covers all resource types, action constraints, parameter semantics, and dry_run behavior. It also points to sibling tools for adjacent use cases, making selection and invocation unambiguous.

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?

All 13 parameters are meaningfully explained in the Args section, including action-specific meanings (e.g., items for add_items vs remove_items) and dry_run default. Since schema description coverage is 0%, the description fully compensates and provides essential context.

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 it 'Manage DNS security resources' and enumerates specific resource types (policies, named lists, application filters, etc.). It also distinguishes from siblings by explicitly directing posture assessment and threat investigation to other tools.

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 explicitly says 'USE THIS for security policy CRUD' and names alternatives: assess_security_posture and investigate_threat. It also clarifies when not to use it (e.g., policies are read-only) and specific constraints for category filters.

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/iracic82/infoblox-ddi-mcp'

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