This record as markdown: /tools/io-github-devopam-mcpg/disable-data-checksums.md
What disable_data_checksums does on Mcpg
AI agents use disable_data_checksums to create or update resources in Mcpg, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcpg environment.
Why disable_data_checksums is rated Medium
Disabling checksums modifies database configuration reversibly (can be re-enabled), affecting data integrity verification rather than deleting data or executing arbitrary code. This is a Write operation because it changes system state. Severity is medium because disabling checksums could allow undetected data corruption to propagate, but the action itself is reversible and doesn't directly cause data loss.
From the tool's definition Tool name 'disable_data_checksums' indicates modification of database integrity settings. No description provided to clarify exact behavior.
Attacks that exploit this kind of access
The rule that runs disable_data_checksums safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For disable_data_checksums, this is the rule to start with:
disable_data_checksums 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every disable_data_checksums call is checked against it from then on.
Questions about disable_data_checksums
disable_data_checksums is a write tool on the Mcpg MCP server. It is categorised as a Write tool in the Mcpg MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcpg MCP server in PolicyLayer and add a rule for disable_data_checksums: 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 Mcpg. Nothing to install.
disable_data_checksums 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 disable_data_checksums 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 disable_data_checksums. 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.
disable_data_checksums is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue