Low Risk

cb_get_asset

Obtém um asset específico do Content Builder do SFMC pelo ID, incluindo conteúdo completo e metadados.

Part of the Ljit Mcp Sfmc server.

cb_get_asset is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE LJIT MCP SFMC →

Free to start. No card required.

AI agents call cb_get_asset to retrieve information from Ljit Mcp Sfmc without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though cb_get_asset only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cb_get_asset": {}
  }
}

See the full Ljit Mcp Sfmc policy for all 40 tools.

Get this rule live on your own Ljit Mcp Sfmc server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY LJIT MCP SFMC →

View all 40 tools →

These attack patterns abuse exactly the kind of access cb_get_asset gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so cb_get_asset only ever does what you allow.

SECURE LJIT MCP SFMC →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the cb_get_asset tool do? +

Obtém um asset específico do Content Builder do SFMC pelo ID, incluindo conteúdo completo e metadados.. It is categorised as a Read tool in the Ljit Mcp Sfmc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cb_get_asset? +

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

What risk level is cb_get_asset? +

cb_get_asset is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cb_get_asset? +

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

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

cb_get_asset is provided by the Ljit Mcp Sfmc MCP server (ljit-mcp-sfmc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ljit Mcp Sfmc tool call.

Deterministic rules across all 40 Ljit Mcp Sfmc tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.