New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

dr_send_linkedin_conversion

Send a LinkedIn Conversions API event. Required: access_token, conversion_id (or conversion_urn). LinkedIn CAPI requires SHA-256 hashed email or phone — li_fat_id alone is insufficient (will skip with

SERVER0nmcp SOURCE0nmcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-0nork-0nmcp/dr-send-linkedin-conversion.md

What dr_send_linkedin_conversion does on 0nmcp

AI agents use dr_send_linkedin_conversion to create or update resources in 0nmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 0nmcp environment.

Why dr_send_linkedin_conversion is rated Medium

An AI agent can call dr_send_linkedin_conversion faster than any human can review: one bad instruction and it creates or modifies resources in 0nmcp by the hundred, each call as confident as the last.

Questions about dr_send_linkedin_conversion

What does the dr_send_linkedin_conversion tool do? +

Send a LinkedIn Conversions API event. Required: access_token, conversion_id (or conversion_urn). LinkedIn CAPI requires SHA-256 hashed email or phone — li_fat_id alone is insufficient (will skip with. It is categorised as a Write tool in the 0nmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dr_send_linkedin_conversion? +

Register the 0n MCP server in PolicyLayer and add a rule for dr_send_linkedin_conversion: 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 0nmcp. Nothing to install.

What risk level is dr_send_linkedin_conversion? +

dr_send_linkedin_conversion is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dr_send_linkedin_conversion? +

Yes. Add a rate_limit block to the dr_send_linkedin_conversion 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.

How do I block dr_send_linkedin_conversion completely? +

Set action: deny in the PolicyLayer policy for dr_send_linkedin_conversion. 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.

What MCP server provides dr_send_linkedin_conversion? +

dr_send_linkedin_conversion is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on 0n, and thousands of servers like it.

This server

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 0n's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.