saml_decode
Decode and inspect SAML 2.0 messages for SSO debugging: paste a SAMLResponse / SAMLRequest (base64 from an HTTP-POST form, deflated + URL-encoded from an HTTP-Redirect URL, the whole redirect URL, or raw XML) or IdP / SP metadata. Returns the message type, issuer, destination, status, every asser...
This record as markdown: /tools/com-it-scorptech-x402/saml-decode.md
What saml_decode does on ScorpTech x402 API
AI agents call saml_decode to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
now | integer | — | Unix time used for validity checks (default: now) |
saml | string | Yes | SAMLResponse / SAMLRequest (base64, deflated base64, URL-encoded), a redirect URL, raw XML or metadata XML |
includeXml | boolean | — | Return the decoded, pretty-printed XML |
Parameters from the server's own tool schema.
Why saml_decode is rated Low
Even though saml_decode only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs saml_decode safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For saml_decode, this is the rule to start with:
saml_decode is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every saml_decode call is checked against it from then on.
Questions about saml_decode
Decode and inspect SAML 2.0 messages for SSO debugging: paste a SAMLResponse / SAMLRequest (base64 from an HTTP-POST form, deflated + URL-encoded from an HTTP-Redirect URL, the whole redirect URL, or raw XML) or IdP / SP metadata. Returns the message type, issuer, destination, status, every assertion (NameID and format, subject confirmation, conditions with NotBefore / NotOnOrAfter checked against now, audiences, AuthnContext, session index, attributes), signature placement and algorithms, embedded certificates (subject, expiry, SHA-256 fingerprint) and metadata endpoints. Flags unsigned responses, SHA-1, signature references that do not cover their parent (XML Signature Wrapping), multiple assertions, comments inside NameID, expired conditions and expired certificates. DTDs are rejected (XXE-safe); signatures are inspected, not cryptographically verified. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/saml-decode. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
saml_decode accepts 3 parameters: now, saml, includeXml. Required: saml. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for saml_decode: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ScorpTech x402 API. Nothing to install.
saml_decode is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the saml_decode rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for saml_decode. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
saml_decode is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue