chat_with_my_agent
Send a test message to one of YOUR OWN agent TEMPLATES. This is the creator conversation returned by agent_messages, not chat_with_instance
This record as markdown: /tools/io-github-proagentstore-platform/chat-with-my-agent.md
What chat_with_my_agent does on ProAgentStore
AI agents use chat_with_my_agent to create or update resources in ProAgentStore, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ProAgentStore environment.
Why chat_with_my_agent is rated Medium
Tool sends test messages to user-owned agent templates, creating transient log entries without persistent state modification.
From the tool's definition Send a test message to one of YOUR OWN agent TEMPLATES.
Attacks that exploit this kind of access
The rule that runs chat_with_my_agent 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 chat_with_my_agent, this is the rule to start with:
chat_with_my_agent stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 chat_with_my_agent call is checked against it from then on.
Questions about chat_with_my_agent
Send a test message to one of YOUR OWN agent TEMPLATES. This is the creator conversation returned by agent_messages, not chat_with_instance. It is categorised as a Write tool in the ProAgentStore MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for chat_with_my_agent: 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.
chat_with_my_agent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the chat_with_my_agent 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 chat_with_my_agent. 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.
chat_with_my_agent 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