Response
What the agent receives after execution, or in its place.
On success, the agent receives the real result of the MCP server, as a JSON-RPC response with the same id as the message it sent. Xokepoint does not change the content of the result.
Xokepoint opens its own session with the server and negotiates the protocol on its side. Protocol and client metadata of the incoming message are removed, and the business parameters stay the same. For the server, the caller is Xokepoint.
Without execution, the response depends on the reason, as shown in Failure semantics. A DENY returns as HTTP 200 with a JSON-RPC access denied error. The detailed reason, such as no_resource, stays in the decision trace and does not go to the agent: it would tell a malicious agent which relation is missing.
A server failure after ALLOW returns as 502, with no automatic retry. The tool may have run before the response was lost.