list_signal_proposals
List the AI-generated campaign proposals produced from detected signals, optionally filtered by status (pending, approved, rejected, modified, launched, expired). An unknown status is ignored and all proposals are returned. Returns {data: SignalProposal[]}. Review pending proposals before approvi...
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/list-signal-proposals.md
What list_signal_proposals does on Max MCP Server
AI agents call list_signal_proposals to retrieve information from Max MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_signal_proposals is rated Low
This tool retrieves and filters existing campaign proposals without creating, modifying, deleting, or executing external operations. It is a straightforward data query with no side effects, fitting the Read category. Severity is low because listing proposals poses minimal risk even if an AI agent misuses it—the worst outcome is viewing unwanted data.
From the tool's definition Tool description uses 'List' verb and states it returns data ({data: SignalProposal[]}). The function is explicitly read-only: 'optionally filtered by status' with no modification operations mentioned.
Attacks that exploit this kind of access
The rule that runs list_signal_proposals safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_signal_proposals, this is the rule to start with:
list_signal_proposals 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 Max MCP Server, apply this rule, and every list_signal_proposals call is checked against it from then on.
Questions about list_signal_proposals
List the AI-generated campaign proposals produced from detected signals, optionally filtered by status (pending, approved, rejected, modified, launched, expired). An unknown status is ignored and all proposals are returned. Returns {data: SignalProposal[]}. Review pending proposals before approving them. It is categorised as a Read tool in the Max MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for list_signal_proposals: 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 Max MCP Server. Nothing to install.
list_signal_proposals 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 list_signal_proposals 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 list_signal_proposals. 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.
list_signal_proposals is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
This server
Across the catalogue