Skip to main content
Glama
CoveoSec
by CoveoSec

hash_exceptions_blocklist

Add SHA256 hashes to a block list to stop malicious files from executing. Use it when a file is not on an existing allow or block list.

Instructions

Block List Files

Add files which do not exist in the allow or block lists to a block list. You can view the block list in the UI at Incident Response > Action Center > Block List.

Required license: Cortex XSIAM Premium or Cortex XSIAM Enterprise or Cortex XSIAM Enterprise Plus

[POST /public_api/v1/hash_exceptions/blocklist] · Response Action

Example request body:

{
  "request_data": {
    "hash_list": [
      "032196FB1A---DFCF69E5D553F0",
      "365296EB1B---FCF69E7D553E4",
      "365296EB1B---FCF69E5D523E4",
      "365296EB1B---FCF69E5D553D4",
      "365296EB1B---FCF63E5D553D4"
    ],
    "comment": "test",
    "incident_id": 5
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
request_dataYesA dictionary containing the API request fields.
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the endpoint, required license, and UI location, but does not mention permissions, reversibility, idempotency, or response behavior. For a mutating action, this is a significant transparency gap.

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?

The description is well-structured with a purpose statement, UI location, license requirement, endpoint, and example body. It avoids unnecessary fluff, though the initial 'Block List Files' header is somewhat redundant with the tool name.

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 the moderate complexity (nested object, no output schema) and lack of annotations, the description covers prerequisites and provides an example, but it omits success/error behavior and how this tool relates to the allowlist sibling. It is minimally viable but has clear gaps.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents each parameter. The description adds an example request body that reinforces parameter structure but does not provide new semantic meaning beyond what the schema already states. Baseline 3 is appropriate.

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 action: 'Add files which do not exist in the allow or block lists to a block list.' This includes a specific verb (add), a resource (files / block list), and a scope condition, distinguishing it from the sibling hash_exceptions_allowlist tool.

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 implies usage for blocking files and provides a precondition (files must not already be in allow/block lists), but it does not explicitly mention when not to use it or alternatives such as the allowlist tool. Context is clear but exclusions are absent.

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/CoveoSec/xsiam-mcp'

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