get_signal_proposal
Fetch a single signal proposal by id, including its full recommendation (campaign name/description, workflow_config, target_prospect_ids, estimated contacts/credits, matched ICP, and entity). Returns {data: SignalProposal}, or a 404 error if not found.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/get-signal-proposal.md
What get_signal_proposal does on Max MCP Server
AI agents call get_signal_proposal 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 get_signal_proposal is rated Low
This tool retrieves and queries existing proposal data without altering, executing, or destroying it. It is a straightforward read operation that queries a proposal by ID and returns its details. No reversible or irreversible modifications are performed. The blast radius of misuse is minimal—an agent could access proposal data it shouldn't, but cannot modify or delete it.
From the tool's definition 'Fetch a single signal proposal by id' - the verb 'Fetch' and action of retrieving data with no mention of modification, deletion, or execution. Returns data (SignalProposal object) with no side effects.
Attacks that exploit this kind of access
The rule that runs get_signal_proposal 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 get_signal_proposal, this is the rule to start with:
get_signal_proposal 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 get_signal_proposal call is checked against it from then on.
Questions about get_signal_proposal
Fetch a single signal proposal by id, including its full recommendation (campaign name/description, workflow_config, target_prospect_ids, estimated contacts/credits, matched ICP, and entity). Returns {data: SignalProposal}, or a 404 error if not found. 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 get_signal_proposal: 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.
get_signal_proposal 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_signal_proposal 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_signal_proposal. 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_signal_proposal 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