Skip to main content
Glama
Sign In
adversarial-rea

adversarial-rea

by Cultistsid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

check_security

Inspect a target binary for PIE, NX, stack canary, RELRO, and FORTIFY protections to determine its exploitation hardening before manual triage.

Instructions

Check binary security mitigations (PIE, NX, canary, RELRO, FORTIFY)

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": {
      "target_path": "<target_path>"
    },
    "name": "check_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_pathYesPath to target binary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 the burden, and it does convey that this is a non-destructive inspection whose report covers five named mitigations. It is silent on what happens for non-ELF/PE or unsupported files, whether mitigations are reported as booleans or narrative, and whether symbols/stripped binaries affect results.

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?

One compact sentence that front-loads the verb and immediately lists the five checks, with zero filler or restatement of the name.

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

Completeness4/5

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

For a one-parameter read-only inspection tool with full schema coverage and no output schema, the description is nearly sufficient. The remaining gap is the expected report shape and file-type applicability, which an agent would want before deciding this is the right call.

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?

There is a single parameter with 100% schema description coverage ('Path to target binary'), so the schema already does the work. The description adds no format details, accepted path types, or constraints on the target, so the baseline of 3 applies.

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 states a specific verb ('Check') and resource ('binary security mitigations') and enumerates exactly what it inspects: PIE, NX, canary, RELRO, FORTIFY. This is far more specific than the surrounding analysis siblings, though it never explicitly contrasts itself with near-neighbors like analyze_binary or find_dangerous_patterns.

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?

Usage is only implied: the mitigation list suggests you call this for a security posture read rather than for symbols or disassembly. There is no explicit when-to-use, no mention of when a different sibling is preferable (e.g. find_dangerous_patterns), and no stated prerequisites such as the target being an executable.

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