🗄️ Data management tool for cache operations, data export, validation, and cleanup.
AI agents call data_query to retrieve information from MCP Sigmund without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool primarily performs Read operations (data export, validation, cache queries). However, 'cleanup' introduces ambiguity about whether deletions are possible. Severity is medium rather than high because: (1) it operates on financial data which carries inherent sensitivity, (2) the Open Banking context implies regulated personal financial information, and (3) even read-only access to transaction history and…
From the tool's definition Tool description states 'cache operations, data export, validation, and cleanup' with emphasis on data management and export.
Attacks that exploit this kind of access
🗄️ Data management tool for cache operations, data export, validation, and cleanup. It is categorised as a Read tool in the MCP Sigmund MCP Server, which means it retrieves data without modifying state.
Register the MCP Sigmund MCP server in PolicyLayer and add a rule for data_query: 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 MCP Sigmund. Nothing to install.
data_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the data_query 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 data_query. 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.
data_query is provided by the MCP Sigmund MCP server (radup/mcp-sigmund). 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 →