Skip to main content
Glama

execute_security_code

Run custom Python scripts in an isolated sandbox with full access to proxy and browser tools for automating complex security tests like race conditions, blind SQL injection, and exploit chains.

Instructions

Execute a Python script in an isolated sandbox with full access to all other tools via NdpSDK.

REQUIRES: approved=true (human must approve arbitrary code execution).

WHEN TO USE THIS (instead of individual tools):

  • Race conditions / TOCTOU attacks (need precise timing)

  • Blind SQL injection (needs hundreds of sequential requests with conditional logic)

  • Multi-step exploit chains (login → extract token → IDOR scan → report)

  • Heavy loops (brute force, enumeration)

  • Complex encoding/decoding chains (double URL encoding, JWT manipulation)

  • Custom PoC/exploit generation

HOW TO USE NdpSDK:

from nodriver_proxy_mcp.sdk import NdpSDK
import asyncio

async def main():
    sdk = NdpSDK()  # auto-connects to running proxy and browser sessions

    # All 38 other tools are available as async methods:
    await sdk.manage_proxy("start")
    await sdk.browser_open()
    await sdk.browser_go("https://target.com")
    flows = await sdk.get_traffic_summary()
    result = await sdk.replay_flow(flow_id, replacements=[...])

asyncio.run(main())

RESOURCE LIMITS: 256MB memory, 60s CPU time, 32KB output cap. External packages can be auto-installed via the dependencies parameter.

Args: script_content: Python code to execute. Use NdpSDK to access all proxy/browser tools programmatically. dependencies: Pip packages to install before execution (e.g. ["pyjwt", "pycryptodome", "beautifulsoup4"]). timeout: Maximum wall-clock execution time in seconds (default: 300 = 5 minutes). approved: MUST be true. Set this ONLY after the human user has explicitly approved code execution. bypass_proxy: If true, HTTP requests from the script skip the proxy (for raw speed or avoiding interception loops).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeoutNo
approvedNo
bypass_proxyNo
dependenciesNo
script_contentYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description carries the full burden of disclosure and does so thoroughly. It reveals the isolated sandbox nature, resource limits (256MB, 60s CPU, 32KB output), the require for human approval, proxy bypass behavior, and automatic dependency installation. These details go well beyond what any annotation would provide.

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 long but every section earns its place: an introductory summary, explicit use cases, a code example, resource limits, and parameter explanations. It is well-structured with clear headers and code blocks, making it highly scannable despite its length.

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?

This is a complex, powerful tool with 5 parameters and a required human approval gate. The description covers usage scenarios, SDK integration, resource constraints, and safety requirements. Since an output schema exists, the lack of return value explanation is not a gap. The description is complete for agent decision-making and safe invocation.

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?

Although the input schema has 0% description coverage, the description compensates fully by explaining each parameter inline: script_content (Python code using NdpSDK), dependencies (pip packages), timeout (default 300), approved (must be true only after human approval), and bypass_proxy (skips proxy). This adds meaning far beyond the bare schema titles and defaults.

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 tool's purpose: 'Execute a Python script in an isolated sandbox with full access to all other tools via NdpSDK.' It uses a specific verb (execute), identifies the resource (Python script), and distinguishes itself from sibling tools by positioning it as the programmatic orchestration layer for all 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 includes an explicit 'WHEN TO USE THIS (instead of individual tools)' section listing concrete scenarios like race conditions, blind SQL injection, and multi-step exploit chains. It also states the prerequisite that approved must be true, giving clear guidance on when and how to use the tool versus alternatives.

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/BobongKu/nodriver-proxy-mcp'

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