proactive_context
Return tool/workflow candidates ranked by a deterministic heuristic over the current time of day, day of week,
This record as markdown: /tools/io-github-heznpc-iconnect/proactive-context.md
What proactive_context does on Iconnect
AI agents call proactive_context 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 proactive_context is rated Low
This tool retrieves and ranks workflow/tool suggestions based on temporal context. It performs no side effects, does not execute operations, and does not modify data. The deterministic heuristic is a query operation that returns recommendations for human or agent decision-making, placing it squarely in the Read category.
From the tool's definition Tool returns ranked candidates using a deterministic heuristic based on temporal data (time of day, day of week). Description indicates retrieval/ranking operation with no modification or execution of external systems.
Attacks that exploit this kind of access
The rule that runs proactive_context 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 proactive_context, this is the rule to start with:
proactive_context 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 proactive_context call is checked against it from then on.
Questions about proactive_context
Return tool/workflow candidates ranked by a deterministic heuristic over the current time of day, day of week,. 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 proactive_context: 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.
proactive_context 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 proactive_context 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 proactive_context. 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.
proactive_context 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