Which of an edge's tools the policy always denies
const url = 'http://127.0.0.1:8080/v1/tools/resolve';const options = { method: 'POST', headers: { 'Deedglass-Version': '2026-10-01', Authorization: 'Bearer <token>', 'Content-Type': 'application/json' }, body: '{"connector":"scratch","tools":[{"name":"read_text_file","digest":"sha256:1b0e5c1f8a7d6e4b3c2a19f0e8d7c6b5a4f3e2d1c0b9a8f7e6d5c4b3a2f1e0d9"},{"name":"move_file","digest":"sha256:a41c5c1f8a7d6e4b3c2a19f0e8d7c6b5a4f3e2d1c0b9a8f7e6d5c4b3a2f1e0d9"}]}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url http://127.0.0.1:8080/v1/tools/resolve \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --header 'Deedglass-Version: 2026-10-01' \ --data '{ "connector": "scratch", "tools": [ { "name": "read_text_file", "digest": "sha256:1b0e5c1f8a7d6e4b3c2a19f0e8d7c6b5a4f3e2d1c0b9a8f7e6d5c4b3a2f1e0d9" }, { "name": "move_file", "digest": "sha256:a41c5c1f8a7d6e4b3c2a19f0e8d7c6b5a4f3e2d1c0b9a8f7e6d5c4b3a2f1e0d9" } ] }'For MCP wrappers (deedglass mcp wrap, docs/MCP.md): send the tools an MCP server lists, and Deedglass answers, for each, whether the enforced policy denies every call to it from this agent (hidden) or might allow it (visible). It reads the policy’s static structure only: the first rule whose match covers <connector>.<name> decides, a rule with a when can’t be decided ahead of time and counts as visible, and with no covering rule the policy’s default decides. Budgets and Stop are ignored, because they change from minute to minute. MCP annotations are never read. Hiding is a convenience for the model: every call still goes through POST /v1/actions and is decided there. Nothing is recorded. At most 500 tools. An agent key with actions:execute.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Header Parameters
Section titled “Header Parameters”The API version (YYYY-MM-DD). Leave it out to use your org’s pinned version (public routes use the latest). An unknown version is 400 api_version_invalid.
Request Bodyrequired
Section titled “Request Bodyrequired”object
The connector name the wrapper was given (--connector); tools are matched as <connector>.<name>.
S10’s connector type the edge declares; mcp when left out (postgres for Postgres MCP servers).
object
The wrapper’s pinned digest of the tool definition. Recorded nowhere yet; S18 uses it.
Example
{ "connector": "scratch", "tools": [ { "name": "read_text_file", "digest": "sha256:1b0e5c1f8a7d6e4b3c2a19f0e8d7c6b5a4f3e2d1c0b9a8f7e6d5c4b3a2f1e0d9" }, { "name": "move_file", "digest": "sha256:a41c5c1f8a7d6e4b3c2a19f0e8d7c6b5a4f3e2d1c0b9a8f7e6d5c4b3a2f1e0d9" } ]}Responses
Section titled “Responses”One tool_visibility per tool, in request order.
object
The enforced policy version (pv_…); null when no policy is active.
S22, additive: the enforced policy by name and version, for the wrapper’s startup line. Null when no policy is active.
object
Example
{ "object": "list", "data": [ { "object": "tool_visibility", "name": "read_text_file", "tool": "scratch.read_text_file", "visibility": "visible", "rule_id": "allow-scratch-reads", "reason": null }, { "object": "tool_visibility", "name": "move_file", "tool": "scratch.move_file", "visibility": "hidden", "rule_id": null, "reason": "No rule allows this tool, and the policy default is deny." } ], "has_more": false, "next_cursor": null, "policy_version": "pv_01k6w4a3d5f7h9k1n3q5s7v9x1"}Headers
Section titled “Headers”This request’s id. Quote it to support; it matches error.request_id.
The API version this response follows.
validation_failed: the connector name, a tool name or digest, or more than 500 tools.
object
object
One or more calm sentences with the next step.
The request field, query parameter or header the error is about.
On policy_invalid only. Each problem with its line, code and hint.
One finding about a policy file, with its position and the next step. Codes are stable and listed in docs/POLICY_ERRORS.md. In the policy_invalid error envelope each diagnostic also carries object: policy_diagnostic. The full PolicyDiagnostic schema is in openapi.yaml.
object
One agent action. Its sections mirror the deed’s. status is the one field an agent needs; state is the exact lifecycle state (docs/GATE.md). The Gate’s own responses (POST /v1/actions and its result report) add execution.result and witness.reasons; lists leave both out. The full Action schema is in openapi.yaml.
object
On undo_unavailable only. Every check of the undo, each with its fix. Additive (S23).
One of the twelve safety checks (S23 §3.3). Available means no check failed. The full UndoCheck schema is in openapi.yaml.
object
Example
{ "error": { "type": "invalid_request_error", "code": "not_found", "message": "There's no endpoint at GET /v1/helth. Did you mean /v1/health?", "param": null, "request_id": "req_01j9zr3m5k8q2w7x4t6v0b1c9d", "doc_url": "https://docs.deedglass.com/errors/not_found" }}Headers
Section titled “Headers”This request’s id. Quote it to support; it matches error.request_id.
default
Section titled “default”An error. Every error has this envelope; doc_url explains the code.
object
object
One or more calm sentences with the next step.
The request field, query parameter or header the error is about.
On policy_invalid only. Each problem with its line, code and hint.
One finding about a policy file, with its position and the next step. Codes are stable and listed in docs/POLICY_ERRORS.md. In the policy_invalid error envelope each diagnostic also carries object: policy_diagnostic. The full PolicyDiagnostic schema is in openapi.yaml.
object
One agent action. Its sections mirror the deed’s. status is the one field an agent needs; state is the exact lifecycle state (docs/GATE.md). The Gate’s own responses (POST /v1/actions and its result report) add execution.result and witness.reasons; lists leave both out. The full Action schema is in openapi.yaml.
object
On undo_unavailable only. Every check of the undo, each with its fix. Additive (S23).
One of the twelve safety checks (S23 §3.3). Available means no check failed. The full UndoCheck schema is in openapi.yaml.
object
Example
{ "error": { "type": "invalid_request_error", "code": "not_found", "message": "There's no endpoint at GET /v1/helth. Did you mean /v1/health?", "param": null, "request_id": "req_01j9zr3m5k8q2w7x4t6v0b1c9d", "doc_url": "https://docs.deedglass.com/errors/not_found" }}Headers
Section titled “Headers”This request’s id. Quote it to support; it matches error.request_id.
The API version this response follows.