toolpolicy.com
Menu

Safety, Security & Runtime Controls

Tool Policy

Security gateway that enforces access controls, API whitelists, and usage permissions to prevent agents from executing unauthorized tools.

Three Pillars

Why This Becomes Necessary

AI agents can reason and escalate attacks independently, meaning individually low-risk tools can chain into high-impact outcomes without explicit, runtime-enforced permission controls.

What a Solution Must Provide

A production stack needs policy-as-code, ethical enforcement layers, compliance checking at invocation time, signed decision logs, and deterministic intervention mechanisms when a policy breach is detected.

Regulatory & Standards Angle

Human-oversight obligations become operational only when each tool call can be paused, attributed to accountable operators, and verified through compliance checking before execution.

Evidence Ledger

Full ledger →

Developments that demonstrate the practical necessity of agent tool-use governance, policy engines, and containment layers. Primary sources only.

September 10, 2026

Poisoned support article can manipulate LLM-powered agent behavior

An experiment shows that a poisoned support article containing a lie can make an LLM-powered support agent behave incorrectly, without needing to breach the code.

Why this matters

For AI agent tool-use policies, this shows that untrusted content in the agent's context can override intended behavior, so permission systems and guardrails must treat retrieved documents as untrusted inputs and enforce capability restrictions independent of model trust.

prompt injection tool-use policy agent safety context poisoning

September 6, 2026

Tool output untrusted: prompt injection via free-text fields

ARMO Security states that tool output is untrusted and attackers target free-text fields in internal systems such as ticket bodies, opportunity notes, and PR descriptions, which can be exploited for prompt injection.

Why this matters

For AI agent tool-use policies, this means tool outputs must be treated as untrusted input; agent permissions and guardrails should restrict or sanitize free-text fields and prevent tool outputs from overriding instructions.

prompt-injection tool-output agent-safety guardrails

September 2, 2026

Databricks publishes Big Book of AgentOps

Databricks announced the Databricks Big Book of AgentOps, defining AgentOps as the operating discipline for building, deploying and improving AI agents in production, covering architecture, evaluation, observability, governance, security and cost management.

Why this matters

For tool-use policy stakeholders, this positions governance and security as core parts of AgentOps, reinforcing that agent tool permissions and safety guardrails should be treated as first-class production concerns rather than afterthoughts.

agentops governance security agent-safety

September 2, 2026

Malicious npm package posing as Codex UI tool exfiltrated data from 29,000 downloads

Researchers uncovered a malicious npm package posing as a Codex UI tool. Attackers exfiltrated data from over 29,000 downloads.

Why this matters

This illustrates a real supply-chain risk for AI agent tooling: agent owners and policy makers must enforce strict tool permissions, verify package provenance, and apply allowlisting/guardrails to prevent malicious MCP/plugin packages from accessing sensitive data.

Sources

supply-chain npm malicious-package codex tool-permissions agent-safety

Latest Articles

Related Primitives

Explore the Agentic Infrastructure Ecosystem

Relevant: EU AI Act Article 14 - Article 14 requires effective human oversight measures, which tool permission control planes with intervention mechanisms directly operationalize. Source
Research: Forewarned is Forearmed: A Survey on Large Language Model-based Agents in Autonomous Cyberattacks — Minrui Xu et al. Nanyang Technological University / University of Waterloo, 2025.
“Governance/Guardrails for LLM-based Agents: Developing effective governance for LLM-based agents is critical. Unlike traditional tools, these agents can reason and escalate attacks independently. To mitigate risks, agent architectures must embed safety constraints. Research should implement ethical enforcement, compliance checking, and intervention mechanisms.”
Read paper →