🏦 Banking data and analysis tool. Query accounts, transactions, balances, and financial insights from the database. When no provider is specified, queries ALL providers by default. When no account is specified, queries ALL accounts by default.
AI agents call banking_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 retrieves personal financial data (accounts, transactions, balances) from a PostgreSQL database without side effects. While the data sensitivity is high (personal financial information), the operation itself is read-only.
From the tool's definition Tool description states it 'Query accounts, transactions, balances, and financial insights from the database' and 'Provides educational financial analysis tools' — all retrieval operations without modification.
Attacks that exploit this kind of access
🏦 Banking data and analysis tool. Query accounts, transactions, balances, and financial insights from the database. When no provider is specified, queries ALL providers by default. When no account is specified, queries ALL accounts by default. 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 banking_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.
banking_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 banking_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 banking_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.
banking_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 →