spraay_auth_session
Create an authenticated session with scoped permissions and configurable TTL. Returns a session token (spr_...) for use in Authorization headers. Data persists in Supabase. Costs $0.005 USDC.
This record as markdown: /tools/io-github-plagtech-spraay-x402-mcp/spraay-auth-session.md
What spraay_auth_session does on Spraay X402 Mcp
AI agents use spraay_auth_session to commit financial operations through Spraay X402 Mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why spraay_auth_session is rated Critical
Although the primary action is creating a session (Write), the tool explicitly charges $0.005 USDC per invocation, making it a financial commitment. Under the severity rules, Financial outranks Write. Misuse by an AI agent repeatedly calling this tool could drain funds; severity is high given the automated, programmatic nature of the MCP context.
From the tool's definition Costs $0.005 USDC — creates an authenticated session that incurs a financial transaction on each call
Attacks that exploit this kind of access
The rule that runs spraay_auth_session safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Spraay X402 Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spraay_auth_session, this is the rule to start with:
Any call to spraay_auth_session is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Spraay X402 Mcp, apply this rule, and every spraay_auth_session call is checked against it from then on.
Questions about spraay_auth_session
Create an authenticated session with scoped permissions and configurable TTL. Returns a session token (spr_...) for use in Authorization headers. Data persists in Supabase. Costs $0.005 USDC. It is categorised as a Financial tool in the Spraay X402 Mcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Spraay X402 MCP server in PolicyLayer and add a rule for spraay_auth_session: 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 Spraay X402 Mcp. Nothing to install.
spraay_auth_session is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the spraay_auth_session 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 spraay_auth_session. 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.
spraay_auth_session is provided by the Spraay X402 MCP server (spraay-x402-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Spraay X402, and thousands of servers like it.
Across the catalogue