bolsa_notifications_get

Get dashboard notifications and pending actions

SERVERBolsa De Carga SOURCEcargoffer/bolsa_de_carga-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cargoffer-bolsa-de-carga-mcp/bolsa-notifications-get.md

WHAT IT DOES

What bolsa_notifications_get does on Bolsa De Carga

AI agents call bolsa_notifications_get to retrieve information from Bolsa De Carga without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why bolsa_notifications_get is rated Low

This tool retrieves notifications and pending actions from a dashboard—a query operation with no side effects, data modification, or irreversible actions. It falls clearly into the Read category as a safe information retrieval function.

From the tool's definition Tool name 'bolsa_notifications_get' with description 'Get dashboard notifications and pending actions' indicates data retrieval only. The verb 'get' and lack of modification language confirm read-only operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bolsa_notifications_get safely

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

bolsa_notifications_get Allowed

bolsa_notifications_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bolsa_notifications_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about bolsa_notifications_get

What does the bolsa_notifications_get tool do? +

Get dashboard notifications and pending actions. It is categorised as a Read tool in the Bolsa De Carga MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bolsa_notifications_get? +

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

What risk level is bolsa_notifications_get? +

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

Can I rate-limit bolsa_notifications_get? +

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

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

bolsa_notifications_get is provided by the Bolsa De Carga MCP server (cargoffer/bolsa_de_carga-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Bolsa De Carga, and thousands of servers like it.

This server

All 197 Bolsa De Carga tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →