No AI Agent Without Identity (Part 4): Deterministic Boundaries, Revocation, and MCP Enforcement
By
Sebastian Martinez Torregrosa
Source
You might also wanna read
AI Security: Why You Should Treat AI Agents as Untrusted and Build for Containment
The article argues that AI agents should be treated as inherently untrusted and potentially malicious, advocating for security architectures
Critique of the Agent Model: Distinguishing Automation from Genuine Agency in AI Systems
This paper critiques the current AI agent landscape, distinguishing between mere automation and genuine agency. Drawing on Descartes' philos
Critique of the Agent Model: Distinguishing Automation from Genuine Agency in AI Systems
This paper critiques the current AI agent landscape, distinguishing between mere automation and genuine agency. Drawing on Descartes' philos
Know Your Agent (KYA): The Emerging Security Framework for Autonomous AI Verification
This article examines the rise of AI agents as autonomous software systems operating across financial systems, APIs, and enterprise workflow
Exploring the Minimalist Approach: When AI Agents Only Need Code Execution
The article explores the concept of a 'code-only agent' - an AI agent that can only write and execute code, without access to other tools or
Reliable AI agents need deterministic control flow in software, not better prompts
The article argues that building reliable AI agents for complex tasks requires deterministic control flow implemented in software code, rath
Security Risks and Vulnerabilities in Anthropic's Model Context Protocol (MCP)
The article examines security risks and vulnerabilities in Anthropic's Model Context Protocol (MCP), which enables AI systems to connect to
hiddenlayer.com·7mo ago
Comments
Sign in to join the conversation.
No comments yet. Be the first.