AI agents call list to retrieve information from Access and 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 name 'list' combined with its presence among read-oriented tools (query, read_notes) strongly suggests it retrieves or enumerates data without side effects. However, the empty description introduces uncertainty—it could theoretically list database structures, tables, or records depending on implementation. Low severity because listing operations typically have minimal blast radius. Confidence is moderate (0.
From the tool's definition Tool name is 'list' on a database MCP server alongside query, read_notes, and other data access operations. With an empty description, the name suggests enumeration or listing of database contents without modification.
Documented attack patterns abuse exactly the kind of access list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Access and SQLite MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list:
{
"version": "1",
"default": "deny",
"tools": {
"list": {}
}
}list 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.
list. It is categorised as a Read tool in the Access and SQLite MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Access and SQLite MCP Server MCP server in PolicyLayer and add a rule for list: 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 Access and SQLite MCP Server. Nothing to install.
list 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 list 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 list. 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.
list is provided by the Access and SQLite MCP Server MCP server (scanzy/mcp-server-access-mdb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Access and SQLite MCP Server, 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.
11 Access and SQLite MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.