Report an action outcome to Ember for learning. This helps Ember understand what works well and what doesn
AI agents use ember_learn_from_outcome to create or update resources in Agent Runtime — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Runtime environment.
This tool writes/updates an AI learning system by reporting outcomes, modifying its internal model or knowledge base. It creates or modifies state (learning data) reversibly. It does not execute commands, delete data, or involve finances. Confidence is slightly reduced because the description is truncated and full behavior is unclear.
From the tool's definition 'Report an action outcome to Ember for learning. This helps Ember understand what works well and what doesn'
Attacks that exploit this kind of access
Report an action outcome to Ember for learning. This helps Ember understand what works well and what doesn. It is categorised as a Write tool in the Agent Runtime MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent Runtime MCP server in PolicyLayer and add a rule for ember_learn_from_outcome: 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 Agent Runtime. Nothing to install.
ember_learn_from_outcome 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 ember_learn_from_outcome 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 ember_learn_from_outcome. 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.
ember_learn_from_outcome is provided by the Agent Runtime MCP server (marc-shade/agent-runtime-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 →