Create a new attestation schema on Rootstock network
AI agents use create-schema 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.
The tool writes data (a schema definition) to the RSK blockchain. While attestation schemas are governance/configuration artifacts, they are not financial transactions, code execution, or destructive. The operation is reversible (schemas can be updated or deprecated).
From the tool's definition 'Create a new attestation schema on Rootstock network' — this tool creates and persists a new schema object on the blockchain, a reversible write operation.
Attacks that exploit this kind of access
Create a new attestation schema on Rootstock network. 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.
Register the RSK MCP Server - Rootstock Blockchain Tools MCP server in PolicyLayer and add a rule for create-schema: 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.
create-schema 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 create-schema 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 create-schema. 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.
create-schema 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →