AI agents call read_notes 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 'read_notes' tool retrieves stored notes about database files—a read-only operation with no side effects. It falls clearly into the Read category as it queries and retrieves information. Severity is low because reading notes poses minimal risk; an AI agent cannot cause harm by retrieving documentation or metadata. Despite the empty description, the tool name provides sufficient evidence of its read-only nature.
From the tool's definition Tool name 'read_notes' and server context indicate retrieval of database file metadata/notes without modification. No description provided, but name strongly suggests query/retrieval operation.
Documented attack patterns abuse exactly the kind of access read_notes 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 read_notes:
{
"version": "1",
"default": "deny",
"tools": {
"read_notes": {}
}
}read_notes 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.
read_notes. 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 read_notes: 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.
read_notes 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 read_notes 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 read_notes. 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.
read_notes 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.