issue-attestation | PolicyLayer

WHAT IT DOES

What issue-attestation does on RSK MCP Server - Rootstock Blockchain Tools

AI agents use issue-attestation to create or update resources in RSK MCP Server - Rootstock Blockchain Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RSK MCP Server - Rootstock Blockchain Tools environment.

WHY IT NEEDS A POLICY

Why issue-attestation needs a policy

This tool creates a new attestation record on the Rootstock blockchain, which is a reversible write operation (attestations can typically be revoked or invalidated, unlike destructive deletion). The severity is high because attestations represent claims about identity, credentials, or assets—misuse could issue false credentials or fraudulent attestations affecting downstream trust.

From the tool's definition Tool name 'issue-attestation' and description 'Issue a new attestation on Rootstock network using RAS' indicates creation of a new record/credential on-chain. The verb 'Issue' combined with 'new attestation' confirms data creation with blockchain persistence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

issue-attestation Rate-limited

issue-attestation 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-attestation": {
      "limits": [
        {
          "counter": "issue-attestation_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 RSK MCP Server - Rootstock Blockchain Tools, so you can run agents against it safely.

FAQ

Questions about issue-attestation

What does the issue-attestation tool do? +

Issue a new attestation on Rootstock network using RAS (Rootstock Attestation Service). It is categorised as a Write tool in the RSK MCP Server - Rootstock Blockchain Tools 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-attestation? +

Register the RSK MCP Server - Rootstock Blockchain Tools MCP server in PolicyLayer and add a rule for issue-attestation: 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 RSK MCP Server - Rootstock Blockchain Tools. Nothing to install.

What risk level is issue-attestation? +

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

Can I rate-limit issue-attestation? +

Yes. Add a rate_limit block to the issue-attestation 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-attestation completely? +

Set action: deny in the PolicyLayer policy for issue-attestation. 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-attestation? +

issue-attestation is provided by the RSK MCP Server - Rootstock Blockchain Tools MCP server (rsksmart/rsk-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.