What are endpoint filters, and how are they different from MVC filters?

In production I account for ordering, dependency lifetimes, exception behavior, and generated metadata. A filter that returns early can bypass later behavior, and a filter that converts every exception can conflict with centralized ProblemDetails middleware. I use authorization policies for access control and application services for business invariants so jobs and message consumers enforce the same rules. Tests cover filter order, short-circuit responses, thrown exceptions, and route groups with multiple registrations. If developers must inspect several hidden filter layers to explain one response, I simplify the pipeline or move the decision to a more explicit boundary.