Issue a new attenuated capability token for another subject. Use this for controlled delegation or integration setup when a new actor needs scoped access to a resource and action set; the new token is stored immediately and recorded in the ledger. Returns a JSON object with the new token ID, subj...
AI agents use sint__issue_token to create or update resources in SINT Protocol — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SINT Protocol environment.
This tool creates a new capability token and persists it to a ledger, which is a Write action. However, the blast radius is high because issuing tokens grants access rights to resources and actions — a misused or over-permissioned token could enable an unauthorized agent to perform destructive, financial, or other high-severity operations downstream.
From the tool's definition Issue a new attenuated capability token for another subject... the new token is stored immediately and recorded in the ledger. Returns a JSON object with the new token ID, subject, resource, actions, and expiry.
Documented attack patterns abuse exactly the kind of access sint__issue_token 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__issue_token:
{
"version": "1",
"default": "deny",
"tools": {
"sint__issue_token": {
"limits": [
{
"counter": "sint__issue_token_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sint__issue_token stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Issue a new attenuated capability token for another subject. Use this for controlled delegation or integration setup when a new actor needs scoped access to a resource and action set; the new token is stored immediately and recorded in the ledger. Returns a JSON object with the new token ID, subject, resource, actions, and expiry. It is categorised as a Write tool in the SINT Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SINT Protocol MCP server in PolicyLayer and add a rule for sint__issue_token: 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__issue_token is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sint__issue_token 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__issue_token. 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__issue_token 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.