ember_feed_context · Agent Runtime MCP: Risk & Policy

WHAT IT DOES

What ember_feed_context does on Agent Runtime

AI agents use ember_feed_context 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.

WHY IT NEEDS A POLICY

Why ember_feed_context needs a policy

The tool writes contextual information about the current work session into the agent runtime, influencing future guidance and session tracking. It modifies session state (a write operation) rather than reading data or executing commands. The blast radius is low since it only updates context/metadata rather than triggering irreversible actions or financial operations.

From the tool's definition 'Give Ember context about your current work' and 'track session progress' indicate writing/updating session state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ember_feed_context Rate-limited

ember_feed_context 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ember_feed_context": {
      "limits": [
        {
          "counter": "ember_feed_context_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Agent Runtime, so you can run agents against it safely.

FAQ

Questions about ember_feed_context

What does the ember_feed_context tool do? +

Give Ember context about your current work. This helps Ember provide better guidance and track session progress. 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.

How do I enforce a policy on ember_feed_context? +

Register the Agent Runtime MCP server in PolicyLayer and add a rule for ember_feed_context: 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.

What risk level is ember_feed_context? +

ember_feed_context is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ember_feed_context? +

Yes. Add a rate_limit block to the ember_feed_context 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 ember_feed_context completely? +

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

ember_feed_context 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.