coding_sessions_list

List all coding sessions (active + ended) for an instance.

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/coding-sessions-list.md

WHAT IT DOES

What coding_sessions_list does on ProAgentStore

AI agents call coding_sessions_list to retrieve information from ProAgentStore without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why coding_sessions_list is rated Low

This tool performs a read-only query to list coding sessions. It retrieves information about active and ended coding sessions without creating, modifying, deleting, or executing any operations. The action is informational only, making it a Read category tool with low severity due to minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'coding_sessions_list' and description 'List all coding sessions' indicates a retrieval operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs coding_sessions_list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For coding_sessions_list, this is the rule to start with:

coding_sessions_list Allowed

coding_sessions_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "coding_sessions_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every coding_sessions_list call is checked against it from then on.

FAQ

Questions about coding_sessions_list

What does the coding_sessions_list tool do? +

List all coding sessions (active + ended) for an instance. It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on coding_sessions_list? +

Register the ProAgentStore MCP server in PolicyLayer and add a rule for coding_sessions_list: 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 ProAgentStore. Nothing to install.

What risk level is coding_sessions_list? +

coding_sessions_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit coding_sessions_list? +

Yes. Add a rate_limit block to the coding_sessions_list 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.

How do I block coding_sessions_list completely? +

Set action: deny in the PolicyLayer policy for coding_sessions_list. 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.

What MCP server provides coding_sessions_list? +

coding_sessions_list is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →