mureo_state_set_conversion_events

Declare which Meta Insights action_type rows count as THIS

SERVERMureo SOURCElogly/mureo

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/logly-mureo/mureo-state-set-conversion-events.md

WHAT IT DOES

What mureo_state_set_conversion_events does on Mureo

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

RISK

Why mureo_state_set_conversion_events is rated Medium

The tool creates or modifies conversion event declarations, which changes how ad performance is tracked and attributed. While not destructive (reversible) or financial (no money moves directly), it is a Write operation that could significantly impact ad campaign analysis and decision-making if misconfigured by an agent.

From the tool's definition 'Declare which Meta Insights action_type rows count as THIS' indicates the tool modifies or sets conversion event definitions/mappings. This is a write operation that alters configuration state in Meta Insights integration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mureo_state_set_conversion_events safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mureo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mureo_state_set_conversion_events, this is the rule to start with:

mureo_state_set_conversion_events Rate-limited

mureo_state_set_conversion_events stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mureo_state_set_conversion_events": {
      "limits": [
        {
          "counter": "mureo_state_set_conversion_events_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mureo, apply this rule, and every mureo_state_set_conversion_events call is checked against it from then on.

FAQ

Questions about mureo_state_set_conversion_events

What does the mureo_state_set_conversion_events tool do? +

Declare which Meta Insights action_type rows count as THIS. It is categorised as a Write tool in the Mureo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mureo_state_set_conversion_events? +

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

What risk level is mureo_state_set_conversion_events? +

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

Can I rate-limit mureo_state_set_conversion_events? +

Yes. Add a rate_limit block to the mureo_state_set_conversion_events 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 mureo_state_set_conversion_events completely? +

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

mureo_state_set_conversion_events is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mureo, and thousands of servers like it.

This server

All 225 Mureo tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →