query_database
AI agents call query_database to retrieve information from Springboot Test without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'query_database' strongly implies a SELECT-like operation that retrieves data for testing purposes. While the description is empty (lowering confidence slightly), the sibling tools include write/execute tools (execute_dml, run_perf_test, run_stress_test) which are classified separately, suggesting this tool is distinct and read-only.
From the tool's definition Tool name 'query_database' indicates a read operation on a database. No description provided, but the name and context (Spring Boot REST API testing server) suggest data retrieval without modification.
Attacks that exploit this kind of access
query_database. It is categorised as a Read tool in the Springboot Test MCP Server, which means it retrieves data without modifying state.
Register the Springboot Test MCP server in PolicyLayer and add a rule for query_database: 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 Springboot Test. Nothing to install.
query_database 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 query_database 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 query_database. 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.
query_database is provided by the Springboot Test MCP server (kenlin-7/springboot-test-mcp). 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 →