Reject one pending escalated action so it cannot proceed. Use this after review when the request is unsafe, out of policy, or no longer needed; the denial reason is recorded in the audit trail. Returns a confirmation message, or an error if the request ID is unknown.
AI agents call sint__deny to permanently remove resources in SINT Protocol — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Denying a pending action is irreversible in the sense that the escalated request is permanently rejected and cannot be re-approved (it cannot proceed). This is a gate-closing action that permanently blocks the pending operation. While it doesn't delete data in the traditional sense, it irreversibly terminates a workflow item.
From the tool's definition Reject one pending escalated action so it cannot proceed... the denial reason is recorded in the audit trail
Documented attack patterns abuse exactly the kind of access sint__deny gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SINT Protocol, and nothing reaches the server without passing your rules. This is the rule we recommend for sint__deny:
{
"version": "1",
"default": "deny",
"hide": [
"sint__deny"
]
}sint__deny disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Reject one pending escalated action so it cannot proceed. Use this after review when the request is unsafe, out of policy, or no longer needed; the denial reason is recorded in the audit trail. Returns a confirmation message, or an error if the request ID is unknown. It is categorised as a Destructive tool in the SINT Protocol MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SINT Protocol MCP server in PolicyLayer and add a rule for sint__deny: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches SINT Protocol. Nothing to install.
sint__deny is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sint__deny rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for sint__deny. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
sint__deny is provided by the SINT Protocol MCP server (sint-ai/sint-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SINT Protocol, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 SINT Protocol tools catalogued and risk-classified — across an index of 43,000+ MCP servers.