override_get
Inspect a single rule to identify its intended match. Check a new request for an actual hit.
tool · Connected client
Before you start
Find the rule in the override list and copy its ID. To check whether its match actually fires, have a fresh matching request ready afterward.
Access: Your MCP client needs the overrideInspect capability for this tool.
Request
{
"name": "override_get",
"arguments": {
"overrideID": "11111111-1111-4111-8111-111111111111"
}
}overrideID- Use the identifier of the rule you want to inspect.
Illustrative tools/call parameters. Inspect the tool’s inputSchema in tools/list before sending them. Replace the synthetic UUID with the identifier from your own authorized session.
What to look for
Inspect a single rule to identify its intended match. Check a new request for an actual hit.
If the result is unexpected
Use a rule identifier, not a bookmark identifier.
What to check if access is denied
Effects and cleanup
This request reads information; it does not start a test or activate a traffic change. Treat returned metadata and any exported evidence as potentially sensitive.
Same underlying tool: joesproxyctl rule get.
Browse all MCP reference entries →