get_tips
Optional advanced workflows/tips (automation, sharing, art, feedback) separated from the core recovery flow. Pricing is dynamic; check /api/v1/tools.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/get-tips.md
What get_tips does on Delx MCP Server
AI agents call get_tips to retrieve information from Delx MCP Server 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 |
|---|---|---|---|
topic | string | — | Optional topic: general|failure|purpose|heartbeat|daily |
status | string | — | Optional status override (if you already have one) |
blockers | string | — | Optional blockers override |
session_id | string | — | Optional session id to personalize tips based on recent check-ins |
Parameters from the server's own tool schema.
Why get_tips is rated Low
This tool retrieves or queries information about workflows, tips, and pricing—a read-only operation with no side effects. There is no indication it modifies data, executes arbitrary code, deletes anything, or handles financial transactions directly. The mention of 'dynamic pricing' is descriptive context about the tool itself, not an indication that the tool moves money.
From the tool's definition Tool is named 'get_tips' and described as retrieving 'optional advanced workflows/tips' which is a retrieval operation with no modification, deletion, or execution indicated. The reference to checking pricing via an API endpoint is informational lookup.
Attacks that exploit this kind of access
The rule that runs get_tips safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tips, this is the rule to start with:
get_tips 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 Delx MCP Server, apply this rule, and every get_tips call is checked against it from then on.
Questions about get_tips
Optional advanced workflows/tips (automation, sharing, art, feedback) separated from the core recovery flow. Pricing is dynamic; check /api/v1/tools. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
get_tips accepts 4 parameters: topic, status, blockers, session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for get_tips: 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 Delx MCP Server. Nothing to install.
get_tips 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_tips 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_tips. 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_tips is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue