linkedin_raw_request
Send an arbitrary LinkedIn API request via Unipile's magic route. Only GET and POST methods are allowed. WARNING: This bypasses structured rate limiting and can perform destructive actions. Use this only when no other LinkedIn tool covers the needed functionality.
This record as markdown: /tools/io-github-saloprj-dialogbrain/linkedin-raw-request.md
What linkedin_raw_request does on Dialogbrain
AI agents invoke linkedin_raw_request to trigger actions in Dialogbrain. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | — | Request body (for POST requests) |
method | string | — | HTTP method (only GET and POST allowed) |
request_url | string | Yes | Target LinkedIn API endpoint URL |
query_params | object | — | URL query parameters |
Parameters from the server's own tool schema.
Why linkedin_raw_request is rated High
This tool executes arbitrary LinkedIn API requests, bypassing structured rate limiting and safety controls. While only GET and POST are allowed (not DELETE), the description explicitly warns it 'can perform destructive actions' via POST requests.
From the tool's definition 'Send an arbitrary LinkedIn API request', 'Only GET and POST methods are allowed', 'WARNING: This bypasses structured rate limiting and can perform destructive actions'
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs linkedin_raw_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linkedin_raw_request, this is the rule to start with:
linkedin_raw_request stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every linkedin_raw_request call is checked against it from then on.
Questions about linkedin_raw_request
Send an arbitrary LinkedIn API request via Unipile's magic route. Only GET and POST methods are allowed. WARNING: This bypasses structured rate limiting and can perform destructive actions. Use this only when no other LinkedIn tool covers the needed functionality. It is categorised as a Execute tool in the Dialogbrain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
linkedin_raw_request accepts 4 parameters: body, method, request_url, query_params. Required: request_url. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for linkedin_raw_request: 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 Dialogbrain. Nothing to install.
linkedin_raw_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the linkedin_raw_request 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 linkedin_raw_request. 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.
linkedin_raw_request is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
Across the catalogue