AI agents call hasura-query to retrieve information from SettleMint without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Query operations are primarily used to retrieve data from databases or APIs without modifying state. The tool name contains 'query' which is explicitly listed as a Read category example. While the description is uninformative, the context of Hasura (a query/mutation platform) and comparison with sibling mutation tools supports classification as Read rather than Write or Execute.
From the tool's definition Tool name 'hasura-query' indicates a query operation; Hasura is a GraphQL engine used for data retrieval. The empty description limits certainty, but the naming convention and sibling tools (hasura-queries, hasura-mutations) suggest this performs read…
Documented attack patterns abuse exactly the kind of access hasura-query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SettleMint, and nothing reaches the server without passing your rules. This is the rule we recommend for hasura-query:
{
"version": "1",
"default": "deny",
"tools": {
"hasura-query": {}
}
}hasura-query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
hasura-query. It is categorised as a Read tool in the SettleMint MCP Server, which means it retrieves data without modifying state.
Register the SettleMint MCP server in PolicyLayer and add a rule for hasura-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 SettleMint. Nothing to install.
hasura-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 hasura-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 hasura-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.
hasura-query is provided by the SettleMint MCP server (settlemint/sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SettleMint, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
55 SettleMint tools catalogued and risk-classified — across an index of 43,000+ MCP servers.