ask_followup
Ask the Denpex diagnostician a follow-up question about a crash — clarify the fix, explore an alternative, or dig deeper. Pass the original logs and your question; pass back the conversationId from a previous reply to continue the thread. Requires the Team plan or an active trial.
This record as markdown: /tools/denpex-mcp/ask-followup.md
What ask_followup does on Denpex
AI agents call ask_followup to retrieve information from Denpex 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 |
|---|---|---|---|
logs | string | Yes | The original crash logs the question is about. |
history | array | — | Prior turns of this conversation, oldest first. |
question | string | Yes | Your follow-up question. |
conversationId | string | — | From a previous reply, to continue the same thread. |
Parameters from the server's own tool schema.
Why ask_followup is rated Low
Even though ask_followup only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts raw HTML/template content (history[].content)
Attacks that exploit this kind of access
The rule that runs ask_followup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Denpex, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ask_followup, this is the rule to start with:
ask_followup 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 Denpex, apply this rule, and every ask_followup call is checked against it from then on.
Questions about ask_followup
Ask the Denpex diagnostician a follow-up question about a crash — clarify the fix, explore an alternative, or dig deeper. Pass the original logs and your question; pass back the conversationId from a previous reply to continue the thread. Requires the Team plan or an active trial. It is categorised as a Read tool in the Denpex MCP Server, which means it retrieves data without modifying state.
ask_followup accepts 4 parameters: logs, history, question, conversationId. Required: logs, question. The full parameter table on this page comes from the server's own tool schema.
Register the Denpex MCP server in PolicyLayer and add a rule for ask_followup: 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 Denpex. Nothing to install.
ask_followup 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 ask_followup 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 ask_followup. 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.
ask_followup is provided by the Denpex MCP server (denpex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Denpex, and thousands of servers like it.
This server
Across the catalogue