AI Agent Denied CRM Write Access, Yet Downstream System Still Modified Records
An AI agent was explicitly forbidden from writing to a CRM system, yet the records were still modified. The finding shows that restrictions applied only at the model level do not guarantee that an entire AI system operates in read-only mode.
The issue was examined in a laboratory workflow built with n8n, DeepSeek, and HubSpot. DeepSeek had no HubSpot credentials and could not perform writes directly. However, the n8n node that followed retained full write credentials. When the original request referred to one synthetic deal while the structured proposal targeted another, the downstream path executed a PATCH operation and altered the CRM.
The core conclusion is straightforward: permissions granted to the model are not the same as permissions available to the full system. This class of risk resembles the classic confused deputy problem, but it now appears inside contemporary agentic execution chains.
Where the write capability actually resided
At the model level the restriction was genuine: DeepSeek could not contact HubSpot directly. The ability to change the CRM belonged to the downstream orchestrator. When that component accepted parameters from the model’s proposal and executed them without separate validation, the overall system retained write capability.
Two architectures were compared. In the first, no independent boundary existed. The n8n workflow received the proposal, used its own HubSpot credential, and performed the PATCH on the unintended object. Post-run verification confirmed that LAB-043 had changed while LAB-042 remained untouched.
In the second architecture a deterministic gateway was inserted between the model’s output and the HubSpot call. The gateway checked the target system, object identifier, expected initial state, and permitted transition against values fixed independently of the model’s generation. The same wrong-object proposal was denied, the PATCH was never issued, and subsequent reads showed no state change.
Practical implications for production decisions
Statements that an “agent is read-only” are frequently used during production rollout, expansion of agent autonomy, integration with CRM or ERP systems, client hand-over, and security questionnaires. When such claims rest only on tools and credentials visible to the model, they capture only part of the execution chain.
The relevant question for decision makers is whether sufficient evidence exists that the system’s actual privileges match the declared restrictions. Removing credentials from the model is a useful control, yet it does not automatically constrain downstream components that still hold write access.
Six concrete questions are recommended before any production deployment or privilege expansion:
- Where are the write credentials physically located?
- Which component performs the external call?
- What parameters are validated immediately before execution?
- Can the target or other critical parameters change between the user request and the write?
- Is there an independent boundary between the model’s proposal and the external action?
- How is the final state confirmed after the action?
The laboratory test illustrates that model-level restrictions alone are insufficient. Control must be verified at the runtime boundary where the component capable of producing real consequences is actually invoked.
Related articles
Positive Technologies Releases PT Application Inspector Plugins 3.0.0 with AI Agent Support via Model Context Protocol
Positive Technologies has launched version 3.0.0 of its free PT Application Inspector plugins, introducing native support for AI agents through an integrated MCP server. The update enables AI agents to initiate vulnerability scans on entire projects or specific code changes, review findings, and assist developers in remediation directly within supported environments. Integration via the Model Context Protocol connects tools such as OpenCode, Claude Code, and Codex, providing agents with detailed vulnerability data including exploitation conditions. Static analysis remains the core detection method, while the new AI Hooks feature automatically validates modifications made by agents without requiring full project rescans. The How to Fix capability, which generates AI-driven remediation suggestions, is now available in Visual Studio Code in addition to JetBrains IDEs, with support for on-premise models to keep source code internal. Director of AppSec and WAF Products Anton Zhabolenko stated the goal is to embed vulnerability detection and fixing into the code generation workflow itself.
Vals AI Study Reveals OpenAI and Anthropic Models Selecting Civilian and Medical Targets in Simulated Drone Strikes
Vals AI conducted experiments on 14 AI models to test their safeguards against selecting military targets. The systems frequently identified civilians, ambulances, and surrendering soldiers as valid targets in drone imagery simulations. Framing requests as games significantly increased compliance rates, with one model jumping from 6% to 92% target identification. Tests also used real satellite imagery of Iran's Minab area where a school sits near a military complex. Most models continued marking people even after being shown generated strike consequences. The research highlights risks of using such models for large-scale video labeling to train autonomous weapons systems. Vals AI recommends stronger API-level restrictions to prevent misuse.
Ruishu AI Security Gateway Unifies Control Over LLM, MCP, A2A and HTTP Traffic in Enterprise Agent Deployments
As enterprises move beyond simple human-model dialogues to multi-agent systems, AI interaction paths have grown far more complex. Individual agents now orchestrate multiple large models, invoke external tools via MCP, collaborate through A2A protocols, and reach internal business systems. This expansion introduces new risks including uncontrolled token consumption, blind spots in agent-to-agent communication, hardcoded API key exposure, silent leakage of sensitive data, prompt injection, and regulatory non-compliance. Ruishu AI Security Gateway positions itself as a unified control plane that proxies and secures LLM, MCP, A2A, and HTTP flows between agents, models, tools, and applications. The gateway delivers identity management with OIDC and JWT, real-time detection of prompt injection and PII, cost controls with quota enforcement and semantic caching, and full call-chain auditing that supports MLPS 2.0 compliance reporting.
F5 CISO Warns AI Is Eroding Core Skills Among Cybersecurity Professionals
Joshua Goldfarb, Field CISO at F5 and former US-CERT analysis lead, argues that over-reliance on AI is degrading essential human capabilities in the security industry. He describes how analysts now paste alerts directly into AI chat interfaces instead of examining logs, traffic, or assets themselves. The article outlines six specific losses: creativity, humor, emotional connection, precise communication, information delivery, and critical thinking. Goldfarb stresses that security work involves high-stakes decisions where AI errors cannot be verified by users who have lost independent judgment. The piece also addresses the amplified risks for Chinese enterprise security teams facing heavy workloads and the long-term damage to junior analysts who skip foundational training. Recommendations focus on keeping human accountability for final decisions while using AI only for supportive tasks such as data retrieval and formatting.