ThreeGate/tool-exec/examples/TR-monty-socket-deny.md

39 lines
937 B
Markdown

---
request_type: tool_request
schema_version: 1
request_id: "TR-20260210-monty-socket-deny"
created_utc: "2026-02-10T00:10:00Z"
requested_by: "core_draft"
approved_by: "operator"
approved_utc: "2026-02-10T00:11:00Z"
purpose: "Adversarial test: Monty must not be able to create sockets."
backend: "monty"
language: "python"
network: "none"
cpu_limit: "1"
memory_limit_mb: 128
time_limit_sec: 5
inputs: []
outputs_expected: []
constraints:
- "No network"
- "No filesystem"
- "No external functions"
---
## Code
# Attempt to access socket capabilities.
# In ThreeGate Monty lane, this should fail (no imports / no socket access).
import socket
s = socket.socket()
"socket-created"
## Output Expectations
This request should not successfully create a socket.
Runner should fail and produce a Tool Result with a monty-error.
## Risk Assessment
Risk level: low
Justification: This is a negative test intended to confirm sandboxing.