Run all 6 reminder checks — returns list of warnings/blocks based on real DB state
AI agents call cortex_check_reminders to retrieve information from Cortex MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the database state to retrieve and evaluate reminders against check criteria, then returns the results. It has no side effects—it does not create, modify, delete, or execute arbitrary code. The blast radius of misuse is minimal; worst case, an AI agent receives a list of warnings/blocks, which cannot cause harm. This is a Read operation.
From the tool's definition Tool description states 'Run all 6 reminder checks — returns list of warnings/blocks based on real DB state'. The verb 'returns' and the phrase 'checks' indicate retrieval and inspection of existing data with no modification.
Attacks that exploit this kind of access
Run all 6 reminder checks — returns list of warnings/blocks based on real DB state. It is categorised as a Read tool in the Cortex MCP MCP Server, which means it retrieves data without modifying state.
Register the Cortex MCP server in PolicyLayer and add a rule for cortex_check_reminders: 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 Cortex MCP. Nothing to install.
cortex_check_reminders 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 cortex_check_reminders 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 cortex_check_reminders. 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.
cortex_check_reminders is provided by the Cortex MCP server (neuralnexustech/cortex-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 →