Join our Newsletter — 33% off our NHI Course

Could Block’s layered tool pattern curb MCP identity blast radius?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: 200 endpoints show why flat MCP tool catalogs do not scale, in WorkOS case work on Block's Square API demo. Workflow boundaries need separate discovery, planning, and execution so agents do not gain broad action rights from visibility alone.

Editorial analysis by NHI Mgmt Group, based on content published by WorkOS: “MCP Night 2.0 Demo Recap: Block's Goose - The Layered Tool Pattern”.

Key questions

Q: Why does layered tool design improve MCP governance?

A: Layered design improves governance because it separates visibility, workflow planning, and state-changing execution.

Q: How should teams control AI agents that can discover and execute API workflows?

A: Teams should control them by limiting discovery to read-only visibility, constraining planning to approved workflow logic, and reserving execution for narrowly scoped side effects.

Q: What breaks when too many REST endpoints are exposed as MCP tools?

A: When too many REST endpoints are exposed as MCP tools, the model gets a larger, less distinguishable action set and privilege becomes harder to reason about.

Practitioner guidance

  • Bound MCP tools by workflow stage Group discovery, planning, and execution into separate permissioned layers so the agent cannot treat every available capability as a direct action surface.
  • Separate read and write authority Allow tool discovery to enumerate services without granting the same identity permission to invoke side-effecting operations.
  • Reduce endpoint-to-tool fan-out Replace endpoint-level tool publishing with higher-level abstractions when the API estate grows beyond a small, stable surface.

Bottom line: Flat endpoint-to-tool mapping does not scale well once an API platform grows into hundreds of endpoints.

Glossary terms: Layered Tool Pattern, Identity Blast Radius, Method-Level Authorization

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 7 days ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Layered MCP design is a governance pattern, not a developer shortcut. The central insight is that tool abstraction determines how much authority an AI system can exercise with a given identity. When discovery, planning, and execution are separated, the platform stops forcing every endpoint into the same privilege model. Practitioners should treat that separation as part of identity design, not just interface ergonomics.

A few things that frame the scale:

  • 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.

A question worth separating out:

Q: What is the difference between discovery and execution in MCP tool design?

A: Discovery reveals what services and endpoints exist, while execution performs the actual action with validated inputs. They should not share the same authority because visibility alone does not justify state change. Separating them keeps AI agents from turning enumeration into uncontrolled action.

👉 Read our full editorial: Layered MCP tool design shows why endpoint mapping does not scale



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.