▶ Watch ↗18:12
Conference affiliation: Gravitee
Authored by Tim Tyler; published June 4, 2026, and updated June 8, 2026. Explains assembling selected tools and context from multiple systems into workflow-specific MCP servers, with ownership, versioning, change review, scoped authorization, and runtime lineage. The customer-success toolkit is illustrative, not evidence of a deployment. Establishes explanatory authorship, not invention or engineering ownership of MCP composition or Gravitee MCP Studio.
gravitee.ioAuthored by Tyler; published June 18, 2026. Explains an MCP-aware mediation layer that connects enterprise identity to upstream authentication, handles token exchange and consent, checks individual tool calls, and preserves user and agent accountability. This is attributed technical writing, not evidence that Tyler implemented the mediation platform.
gravitee.ioAuthored by Tyler; published July 16, 2026. Explains exporting request and response payloads as OpenTelemetry logs linked to traces through TraceId and SpanId, policy descriptions as span attributes when verbose mode is enabled, and configurable masking before telemetry export. Attributes the explanation to Tyler without assigning him engineering ownership of the release.
gravitee.ioThe retained Gravitee author archive credits Tyler with this July 16, 2026 article and describes centralized OpenTelemetry data masking using detection rules. Its full body is not retained, so attribution and this limited subject description are supported by the archive rather than a complete article review.
gravitee.io · Source ↗The retained Gravitee author archive credits Tyler with this June 19, 2026 introduction to the meaning of API, how APIs work, and REST comparisons. The full article body is not retained; this entry establishes published explanatory work, not API product ownership.
gravitee.io · Source ↗The retained Gravitee author archive credits Tyler with this June 11, 2026 article about Postman as an API client for testing, documentation, and collaboration. The full body is not retained. Authorship does not imply employment at Postman or ownership of its software.
gravitee.io · Source ↗In his first-person account, Tyler identifies himself as Gravitee’s Senior Product Marketing Manager, responsible for positioning, messaging, and sales and marketing enablement. He participates as a human reviewer in a content workflow that drafts from target keywords and a marketing-as-code repository. His review helped identify risks from access to internal information before they became a problem; the team subsequently implemented platform access controls that allowed less review. The evidence establishes participation and review, not that he built the agent, repository, or platform.
gravitee.ioTim Tyler is Senior Product Marketing Manager at Gravitee, where he helps set product positioning and messaging and equips sales and marketing teams to communicate it. His writing explains practical choices in API and AI-agent infrastructure: which tools an agent should receive, whose credentials it uses, and how engineers can investigate failures without exposing sensitive data.
Tyler’s earlier work included helping startups bring products to market alongside research and development and product management teams. He joined Verizon Telematics in 2015, where his product-marketing responsibilities included the small and medium-sized business segment. As Director of Product Marketing, he worked on positioning and brought customer and market perspectives into the company’s communications. His Verizon Connect biography describes a background in product and workforce-management solutions.
At Gravitee, his published work ranges from introductions to APIs and Postman to explanations of agent authorization and OpenTelemetry observability. These articles connect product capabilities to the decisions facing platform teams: how to give agents useful access, keep that access limited, and understand what happened when something goes wrong.
Tyler writes about Model Context Protocol (MCP), which gives agents a structured way to discover and invoke tools. His explanations distinguish choosing the tools an agent can see from checking whether it should be allowed to use them in a particular request.
Tyler also participates in Gravitee’s internal content engine. The agent drafts content from target keywords and uses a marketing-as-code repository containing brand and messaging guidance. Tyler reviews the output for quality and compliance with the team’s expectations.
That review helped identify a separate risk: the agent could reach internal information that should not appear in public marketing copy. The team used Gravitee’s platform to control its access. Tyler describes human review as essential to spotting the risk before it became a problem; the resulting access controls then allowed the team to reduce the amount of review and trust the agent with more of the workflow.
▶ Watch ↗18:12
Loading more talks and highlights…