This record as markdown: /tools/io-github-heznpc-iconnect/read-reminder.md
What read_reminder does on Iconnect
AI agents call read_reminder to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why read_reminder is rated Low
This tool retrieves reminder data by ID without creating, modifying, deleting, or executing actions. It is a pure read operation with minimal blast radius if misused—an agent could only access existing reminder details, not alter system state or commit financial/destructive actions.
From the tool's definition Tool name 'read_reminder' and description 'Read the full details of a specific reminder by ID' explicitly indicate data retrieval with no modification.
Attacks that exploit this kind of access
The rule that runs read_reminder safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_reminder, this is the rule to start with:
read_reminder is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every read_reminder call is checked against it from then on.
Questions about read_reminder
Read the full details of a specific reminder by ID. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for read_reminder: 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 Iconnect. Nothing to install.
read_reminder 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_reminder 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_reminder. 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_reminder is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue