Linux Foundation

How to Grant AI Agents Access to Internal APIs via MCP: Key Questions Security Teams Will Ask

As AI agents increasingly need to call internal APIs, security teams focus on three core questions: who granted access, how to revoke it, and how to investigate incidents after the fact. The answers lie in operation-level access control rather than traffic inspection alone. MCP, now managed by the Agentic AI Foundation under the Linux Foundation, has become the standard for connecting AI agents to enterprise systems with hundreds of millions of SDK downloads monthly. The article details how NEOMSA APIM implements MCP servers, tool publication from OpenAPI specs, subscription-based scopes, and 15 independent security checks. It explains why classic traffic filters fail against valid but unauthorized tool calls and stresses the need for owner approval, application-specific identities, and proper identity propagation through token exchange. Rate limiting at the subscription level and business-object validation are presented as essential controls to prevent overreach and duplication.

Linux Foundation Report Reveals Why Companies Fork Open Source Projects and Maintain Internal Patches

A new Linux Foundation Research study of 567 IT professionals shows that organizations actively modify open source components rather than using them unchanged. While 72% contribute back to projects in some form, many maintain internal forks due to missing features, integration needs, security timelines, and regulatory requirements. The average organization supports 86 internal forks, consuming over 5,000 hours per release cycle. The largest gaps between business-critical technologies and actual contributions appear in programming languages and databases. The findings highlight growing supply-chain risks when internal branches diverge from upstream projects without proper tracking of patches and commits.