create_scheme
AI agents use create_scheme to create or update resources in Government Scheme MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Government Scheme MCP Server environment.
This tool creates new records in a government scheme database. While the description is empty, the name and context clearly indicate write-level data modification. Severity is medium because creating unauthorized or false government scheme entries could mislead citizens about entitlements and benefits, but the action is reversible (can be corrected via update/delete).
From the tool's definition Tool name 'create_scheme' indicates creation of new scheme records. Sibling tools include 'delete_scheme', 'update_scheme', and 'read_scheme', establishing this as a data management system.
Attacks that exploit this kind of access
create_scheme. It is categorised as a Write tool in the Government Scheme MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Government Scheme MCP Server MCP server in PolicyLayer and add a rule for create_scheme: 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 Government Scheme MCP Server. Nothing to install.
create_scheme 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_scheme 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_scheme. 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_scheme is provided by the Government Scheme MCP Server MCP server (magicstack-llp/gov-scheme-mcp-py). 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 →