check_assets

POST /v5/assets/check. Current Bannerbear V5 operation; provider scopes, locks and credits apply. Read operation.

SERVERBannerbear Mcp Cli SOURCE@thenavidm/bannerbear-mcp-cli

Low RISK CLASS

Category Read

Parameters 30 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/thenavidm-bannerbear-mcp-cli/check-assets.md

WHAT IT DOES

What check_assets does on Bannerbear Mcp Cli

AI agents call check_assets to retrieve information from Bannerbear Mcp Cli without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`account`	string	—	Exact private workspace profile label; no fallback to another profile key.
`payload`	object	—	Complete current native JSON body. Use payload or payload_file exclusively.
`payload_file`	string	—	Regular non-symlink local JSON file, at most 1 MiB.

Parameters from the server's own tool schema.

RISK

Why check_assets is rated Low

Even though check_assets only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAccepts raw HTML/template content (payload)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_assets safely

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

check_assets Allowed

check_assets 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": {
    "check_assets": {}
  }
}

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

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

FAQ

Questions about check_assets

What does the check_assets tool do? +

POST /v5/assets/check. Current Bannerbear V5 operation; provider scopes, locks and credits apply. Read operation. It is categorised as a Read tool in the Bannerbear Mcp Cli MCP Server, which means it retrieves data without modifying state.

What parameters does check_assets accept? +

check_assets accepts 3 parameters: account, payload, payload_file. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on check_assets? +

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

What risk level is check_assets? +

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

Can I rate-limit check_assets? +

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

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

check_assets is provided by the Bannerbear Mcp Cli MCP server (@thenavidm/bannerbear-mcp-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Bannerbear Mcp Cli, and thousands of servers like it.

This server

All 75 Bannerbear Mcp Cli tools →

Across the catalogue

The MCP Attack Database →

Guides

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