my_agents
List agents owned by the authenticated ProAgentStore creator.
This record as markdown: /tools/io-github-proagentstore-platform/my-agents.md
What my_agents does on ProAgentStore
AI agents call my_agents 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.
Why my_agents is rated Low
This tool simply lists/retrieves data (agents owned by the authenticated user) without creating, modifying, deleting, or executing anything. It is a straightforward query operation with minimal risk even if misused, as it only returns information already accessible to the authenticated user. The blast radius is low—an AI agent could at worst enumerate the user's agents, which is informational only.
From the tool's definition Tool name 'my_agents' and description 'List agents owned by the authenticated ProAgentStore creator' indicate a read-only retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs my_agents 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 my_agents, this is the rule to start with:
my_agents 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 ProAgentStore, apply this rule, and every my_agents call is checked against it from then on.
Questions about my_agents
List agents owned by the authenticated ProAgentStore creator. It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for my_agents: 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.
my_agents 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 my_agents 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 my_agents. 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.
my_agents 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.
More on ProAgentStore, and thousands of servers like it.
This server
Across the catalogue