SQLite 데이터베이스에서 SELECT 쿼리를 실행하여 데이터를 조회합니다. WHERE 절을 포함한 복잡한 쿼리를 지원합니다.
AI agents call select_data to retrieve information from SQLite MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool executes SELECT queries to read data from a SQLite database. SELECT is a read-only operation with no side effects. However, since it supports 'complex queries including WHERE clauses' and runs arbitrary SQL, there is a slight concern that it could be abused with subqueries or functions, but fundamentally it is a read operation. Severity is low as misuse only exposes data, not modifies it.
From the tool's definition SELECT 쿼리를 실행하여 데이터를 조회합니다 (executes SELECT queries to retrieve data)
Attacks that exploit this kind of access
SQLite 데이터베이스에서 SELECT 쿼리를 실행하여 데이터를 조회합니다. WHERE 절을 포함한 복잡한 쿼리를 지원합니다. It is categorised as a Read tool in the SQLite MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SQLite MCP Server MCP server in PolicyLayer and add a rule for select_data: 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 SQLite MCP Server. Nothing to install.
select_data 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 select_data 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 select_data. 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.
select_data is provided by the SQLite MCP Server MCP server (yuchoe/sqlite-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 →