save-streaming-results
AI agents use save-streaming-results to create or update resources in RateSpot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RateSpot MCP Server environment.
This tool creates or modifies persisted data (saved results) without irreversibly deleting it, fitting the Write category. Severity is medium because misuse could store incorrect mortgage rate data or financial information, leading to downstream decisions based on corrupted/manipulated data, but the write itself is reversible.
From the tool's definition Tool name 'save-streaming-results' indicates persistence of data; context shows server provides mortgage rate APIs and streaming results.
Attacks that exploit this kind of access
save-streaming-results. It is categorised as a Write tool in the RateSpot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RateSpot MCP Server MCP server in PolicyLayer and add a rule for save-streaming-results: 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 RateSpot MCP Server. Nothing to install.
save-streaming-results is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save-streaming-results 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 save-streaming-results. 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.
save-streaming-results is provided by the RateSpot MCP Server MCP server (zad0xlik/ratespot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →