issue_access_token · S2 StreamStore MCP Server MCP

WHAT IT DOES

What issue_access_token does on S2 StreamStore MCP Server

AI agents use issue_access_token to create or update resources in S2 StreamStore MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your S2 StreamStore MCP Server environment.

WHY IT NEEDS A POLICY

Why issue_access_token needs a policy

This tool creates new access tokens, which are reversible but sensitive authentication credentials. While not destructive (tokens can be revoked) or financial, issuing access tokens is a Write operation that modifies the security posture of the system and could enable unauthorized access if scoped incorrectly or issued to hostile actors. High severity reflects the security-relevant nature of credential issuance.

From the tool's definition Tool name 'issue_access_token' and description 'Issue a new access token' indicate creation of a new credential artifact. The mention of 'scope definition' confirms this creates a new access credential with specific permissions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

issue_access_token Rate-limited

issue_access_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "issue_access_token": {
      "limits": [
        {
          "counter": "issue_access_token_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches S2 StreamStore MCP Server, so you can run agents against it safely.

FAQ

Questions about issue_access_token

What does the issue_access_token tool do? +

Issue a new access token. Provide an id and scope definition. It is categorised as a Write tool in the S2 StreamStore MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on issue_access_token? +

Register the S2 StreamStore MCP Server MCP server in PolicyLayer and add a rule for issue_access_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 S2 StreamStore MCP Server. Nothing to install.

What risk level is issue_access_token? +

issue_access_token is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit issue_access_token? +

Yes. Add a rate_limit block to the issue_access_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.

How do I block issue_access_token completely? +

Set action: deny in the PolicyLayer policy for issue_access_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.

What MCP server provides issue_access_token? +

issue_access_token is provided by the S2 StreamStore MCP Server MCP server (s2-streamstore/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.