Skip to main content
Glama
Sign In
HALO (GEMMA-by-GOOGLE)

HALO (GEMMA-by-GOOGLE)

by XenoCoreGiger31
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

run_exploit

Execute custom Python exploit code in an isolated sandbox for penetration testing. Requires operator approval for safe execution.

Instructions

LAST RESORT: run a custom Python PoC in the isolated sandbox runner. Requires operator approval upstream.

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": {
      "code": "<code>"
    },
    "name": "run_exploit"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesFull Python script source.
phaseNo'test' (no network) or 'attack'.test
targetNoTarget ip or ip:port.
timeoutNoSeconds before kill.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Mentions isolated sandbox and operator approval, but lacks details on error handling, return value, or logging. Does not disclose what happens on failure or success.

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?

Extremely concise: two short sentences, front-loaded with 'LAST RESORT'. No redundant information.

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?

Covers main purpose and safety, but fails to explain what happens after execution (e.g., output, results). No output schema, so description should mention return behavior.

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 has 100% coverage with descriptions for all parameters. Tool description adds context (custom PoC, sandbox) but does not enhance parameter semantics beyond what schema provides.

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?

Clearly states the tool runs a custom Python PoC in an isolated sandbox, distinguishing it from sibling tools like run_nmap or run_sqlmap which are specific tools. The 'LAST RESORT' emphasizes its use case.

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?

Explicitly marks as 'LAST RESORT', implying other tools should be tried first, and requires operator approval. Does not name specific alternatives but context from sibling tools provides that.

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