This record as markdown: /tools/io-github-heznpc-iconnect/end-tool-session.md
What end_tool_session does on Iconnect
AI agents invoke end_tool_session to trigger actions in Iconnect. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why end_tool_session is rated High
This tool triggers an external operation — terminating an active session prematurely. It is not purely destructive (sessions expire naturally anyway), but it executes an action with side effects (forcibly ending a session), which could disrupt ongoing operations. It does not create/modify data in a reversible write sense, nor is it purely a read operation.
From the tool's definition End a tool session before its TTL expires
Attacks that exploit this kind of access
The rule that runs end_tool_session 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 end_tool_session, this is the rule to start with:
end_tool_session stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 end_tool_session call is checked against it from then on.
Questions about end_tool_session
End a tool session before its TTL expires. It is categorised as a Execute tool in the Iconnect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Iconnect MCP server in PolicyLayer and add a rule for end_tool_session: 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.
end_tool_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the end_tool_session 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 end_tool_session. 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.
end_tool_session 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.
Across the catalogue