Mastra 1.79.0

Apply these rules to Mastra agents, workflows, tools, MCP integrations, and the server surfaces you expose. Treat @mastra/core as the pack identity; check companion packages against their own APIs and release notes because they have independent versions.

Server identity and authorization

• Configure server.auth for every deployed Mastra API that is not intentionally public. Without it, built-in routes are public; requiresAuth: true does not create an authenticator. Audit requiresAuth: false, customRouteAuthConfig, adapter routes, Studio access, MCP REST routes, and any changed server.apiPrefix. Verify public webhook signatures before using their bodies.
• When using custom server.auth.authenticateToken, verify issuer, audience, signature, and expiry appropriate to the credential. Derive a stable tenant-and-user ownership key from the verified identity with mapUserToResourceId; do not accept memory.resource, thread IDs, or request-body context as proof of ownership. Reject a request when the expected server-derived resource key is absent.
• Carry the authenticated principal in server-owned RequestContext keys and pass it explicitly when invoking an agent or workflow outside an HTTP handler. Derive record filters and outbound credentials inside createTool().execute(inputData, context) or workflow steps from that trusted context; authorize the principal, operation, arguments, and resource at the point of use. A tool schema, model decision, approval click, or instruction is not permission.
• If using Enterprise FGA, configure server.fga permission