Query a Notion database. Args: database_id: Database ID. filter_json: Optional JSON filter string per Notion API spec.
AI agents call notion_query_database to retrieve information from autoMate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from a Notion database using optional filters. It has no side effects, does not modify or delete data, and does not execute arbitrary code. It is a straightforward read operation. Severity is low because querying a database poses minimal risk—the worst case is exposure of sensitive information the user has access to, but the operation itself cannot damage or alter data.
From the tool's definition Tool name contains 'query' and description states 'Query a Notion database' with only filter arguments; no create, update, delete, or execute operations are mentioned.
Documented attack patterns abuse exactly the kind of access notion_query_database gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and autoMate, and nothing reaches the server without passing your rules. This is the rule we recommend for notion_query_database:
{
"version": "1",
"default": "deny",
"tools": {
"notion_query_database": {}
}
}notion_query_database 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.
Query a Notion database. Args: database_id: Database ID. filter_json: Optional JSON filter string per Notion API spec. It is categorised as a Read tool in the autoMate MCP Server, which means it retrieves data without modifying state.
Register the autoMate MCP server in PolicyLayer and add a rule for notion_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 autoMate. Nothing to install.
notion_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 notion_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 notion_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.
notion_query_database is provided by the autoMate MCP server (yuruotong1/automate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 128 autoMate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
128 autoMate tools catalogued and risk-classified — across an index of 42,500+ MCP servers.