AI agents use update to create or update resources in Access and SQLite MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Access and SQLite MCP Server environment.
The 'update' tool modifies database records reversibly. While the description is empty, context from the server description and peer tools (create, query, import/export) confirms this performs write operations on structured data. Severity is high rather than critical because updates are reversible (unlike destructive deletes), but could significantly alter business-critical data if an AI agent is misdirected.
From the tool's definition Tool named 'update' on a database management server (Access and SQLite MCP Server) with sibling tools including 'query', 'create', and 'import'/'export' functions.
Documented attack patterns abuse exactly the kind of access update 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 update:
{
"version": "1",
"default": "deny",
"tools": {
"update": {
"limits": [
{
"counter": "update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
update. It is categorised as a Write tool in the Access and SQLite MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Access and SQLite MCP Server MCP server in PolicyLayer and add a rule for update: 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.
update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update 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 update. 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.
update 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.