pm_disable_freeze
Open private market to public.
This record as markdown: /tools/launch-on-basis-mcp-ts/pm-disable-freeze.md
What pm_disable_freeze does on Basis MCP Server
AI agents use pm_disable_freeze to create or update resources in Basis MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Basis MCP Server environment.
Why pm_disable_freeze is rated Medium
This tool modifies existing market configuration/permissions by removing access restrictions. While it changes system state, it is reversible (the market can be frozen/closed again), so it falls under Write rather than Destructive.
From the tool's definition Tool name 'pm_disable_freeze' and description 'Open private market to public' indicate a state change operation that modifies market access controls from restricted (frozen/private) to unrestricted (public).
Attacks that exploit this kind of access
The rule that runs pm_disable_freeze safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pm_disable_freeze, this is the rule to start with:
pm_disable_freeze stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every pm_disable_freeze call is checked against it from then on.
Questions about pm_disable_freeze
Open private market to public. It is categorised as a Write tool in the Basis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for pm_disable_freeze: 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 Basis MCP Server. Nothing to install.
pm_disable_freeze 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 pm_disable_freeze 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 pm_disable_freeze. 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.
pm_disable_freeze is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Basis MCP Server, and thousands of servers like it.
This server
Across the catalogue