get_preferred_drying_method
AI agents call get_preferred_drying_method to retrieve information from Laundry Timer MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves preference information about drying methods, which is a read-only operation with no destructive, financial, or executable side effects. The empty description reduces confidence slightly, but the name and server context clearly indicate data retrieval functionality. Severity is low because querying personal laundry preferences poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_preferred_drying_method' indicates retrieval of stored preference data. Server description states it 'provides access to laundry preferences,' confirming this tool queries user preferences without modification or side effects.
Attacks that exploit this kind of access
get_preferred_drying_method. It is categorised as a Read tool in the Laundry Timer MCP MCP Server, which means it retrieves data without modifying state.
Register the Laundry Timer MCP server in PolicyLayer and add a rule for get_preferred_drying_method: 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 Laundry Timer MCP. Nothing to install.
get_preferred_drying_method 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 get_preferred_drying_method 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 get_preferred_drying_method. 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.
get_preferred_drying_method is provided by the Laundry Timer MCP server (nicolavs/laundry-timer-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 →