Receive data from an agent
AI agents call receive_agent_data to retrieve information from AgentCraft MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation—it retrieves data from an agent without creating, modifying, or deleting anything. However, severity is elevated to 'medium' rather than 'low' because in a multi-agent system context, receiving data from agents could expose sensitive information depending on what data agents possess, and an AI misusing this to aggregate unauthorized agent data could have moderate impact on confidentiality.
From the tool's definition Tool name 'receive_agent_data' and description 'Receive data from an agent' indicate retrieval of data from another agent without modification. The tool reads/receives data as its primary function.
Attacks that exploit this kind of access
Receive data from an agent. It is categorised as a Read tool in the AgentCraft MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AgentCraft MCP Server MCP server in PolicyLayer and add a rule for receive_agent_data: 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 AgentCraft MCP Server. Nothing to install.
receive_agent_data 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 receive_agent_data 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 receive_agent_data. 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.
receive_agent_data is provided by the AgentCraft MCP Server MCP server (seyhunak/agentcraft-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →