mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-11-18 23:08:26 +01:00
Preserve bounded, redacted and screened upstream JSON-RPC error messages for remote MCP tools and context reads. Audit blocked instructions, retain received error semantics, and redact URL/session and decoded credential echoes. Co-Authored-By: Paperclip <noreply@paperclip.ing>
34 lines
2.3 KiB
Markdown
34 lines
2.3 KiB
Markdown
# Remote MCP call errors
|
|
|
|
The tool gateway maps a top-level JSON-RPC error from a remote tool call or
|
|
context read to HTTP 502 with reason `remote_mcp_error`. It keeps the upstream
|
|
numeric code and the connection identifiers in error details.
|
|
|
|
When the upstream error has a non-empty string message, the gateway appends it
|
|
as `Upstream message (untrusted): ...`. This is provider content, not an
|
|
instruction or a Paperclip policy decision. The message uses the existing secret
|
|
redactors. The gateway also removes known credentials, sensitive request header and query values, and sensitive
|
|
argument values before it clips the provider message
|
|
to 1,000 characters. The shared submitted-value redactor checks percent-decoded
|
|
and Base64/Base64url-decoded spans against known secrets, including credentials
|
|
inside encoded prose, with at most three decoding layers. This covers mixed-case
|
|
and partial URL encoding without changing unrelated text. Control characters are removed. An absent or malformed
|
|
message keeps the generic fallback. The existing result-content prompt-injection
|
|
screen runs on the redacted, bounded text before it is returned or persisted.
|
|
Flagged text uses the generic fallback while keeping the upstream code and
|
|
remote error status. A blocked message writes a company-scoped `tool_gateway.call_failed`
|
|
audit event with guard findings and detector metadata, without the provider text.
|
|
The same configured classifier and regex fallback apply as
|
|
for successful results. Ordinary header and query values are preserved. Query
|
|
secret names combine the URL-vault and existing request redaction rules,
|
|
including code, state, nonce, session and mcp-session-id. Once a complete remote error arrives, its call timer stops; screening
|
|
uses the classifier's own deadline and cannot turn the received error into a
|
|
remote-call timeout.
|
|
|
|
Arbitrary upstream `error.data`, stacks, and raw response bodies are not returned.
|
|
The same safe message is used for caller errors and saved invocation failures.
|
|
HTTP and MCP caller envelopes omit the internal execution audit record.
|
|
This does not change approval, credential, retry, or connection health rules.
|
|
A tool result with `isError: true` still uses the normal result-content validation
|
|
path. Previously saved generic messages cannot recover discarded provider text.
|