Robinhood let AI agents trade real money. The only safety check is optional.
Robinhood's MCP lets an AI agent place real trades with no broker-side cap. A few simple rules at the gateway stop a rogue or hijacked agent draining the account.
18 posts
Robinhood's MCP lets an AI agent place real trades with no broker-side cap. A few simple rules at the gateway stop a rogue or hijacked agent draining the account.
AWS built AgentCore Policy on Cedar: deterministic authorisation at the MCP gateway, outside the LLM loop. The architecture PolicyLayer ships.
The NSA published 17 pages on MCP security. We map every recommendation to where enforcement actually happens: the call path between agent and tool.
Anthropic showed model defences can't stand alone: Claude leaked secrets 24 of 25 times under injection. Why AI agent containment belongs at the environment layer.
Microsoft's Agent Governance Toolkit shipped the cleanest validation of deterministic policy enforcement in agent security: 26.67% violations under prompt-only safety, 0% under AGT. AGT governs one runtime. The harder problem is governance across many.
Oracle has named the category: runtime governance for agentic AI. Their framework is right; their architectural assumption is wrong for most teams. PolicyLayer enforces the same five pillars at the MCP boundary.
Anthropic published the production playbook for MCP: 300M SDK downloads, thin tools over 2,500 endpoints, OAuth vaults. The playbook stops at the tool call. Argument-level policy is what comes next.
Cloudflare's enterprise MCP launch solves discovery, access, and shadow-MCP prevention. That's the baseline. The harder question — what agents are allowed to do once they're inside — needs a different primitive.
Microsoft's open-source toolkit: nine packages for agent policy, identity, and compliance. Review of what works — and the MCP-shaped hole teams must bridge themselves.
MCP policy enforcement intercepts every AI agent tool call and evaluates it against deterministic rules before execution. Here's how it works and how to set it up.
System prompts can't enforce spending limits or prevent destructive operations. Here's why prompt guardrails fail for tool-calling AI agents and what works instead.
Bain & Company's agentic AI architecture framework calls for centralised policy enforcement across MCP tool calls. PolicyLayer is the implementation.
Most teams will wrap their own dangerous tools. The real market for agent control only gets large if agents become dynamic consumers of external services the team did not fully pre-wrap.
Security researchers filed 30+ CVEs against MCP servers in early 2026. Patching individual servers doesn't fix the structural gap. The real fix is a policy layer that works across all of them.
A new research paper argues that LLMs cannot self-enforce security constraints. PolicyLayer implements every recommendation you can deploy today.
Prompt guardrails for MCP agents are bypassable and unauditable. Why deterministic policy enforcement at the transport layer is the real security primitive.
LLMs can't reliably self-enforce safety rules. Deterministic policy enforcement outside the model catches what prompts miss — here's the architecture.
What happens when your AI agent goes rogue? Six failure modes — runaway loops, spending spirals, destructive ops — and the deterministic policies that stop them.