This record as markdown: /tools/io-github-bitsandtea-postking-mcp/list-assets.md
What list_assets does on Postking Mcp
AI agents call list_assets to retrieve information from Postking Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_assets is rated Low
This tool retrieves or queries a list of assets belonging to a brand. There is no indication of creation, modification, deletion, or external execution. The blast radius is minimal—an agent using this tool can only view existing assets, not alter them or trigger external operations.
From the tool's definition Tool name 'list_assets' and description 'List assets in the brand' indicate a retrieval operation with no side effects. The verb 'list' is a standard read operation that queries and returns data without modification.
Attacks that exploit this kind of access
The rule that runs list_assets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postking Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_assets, this is the rule to start with:
list_assets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Postking Mcp, apply this rule, and every list_assets call is checked against it from then on.
Questions about list_assets
List assets in the brand. It is categorised as a Read tool in the Postking Mcp MCP Server, which means it retrieves data without modifying state.
Register the Postking MCP server in PolicyLayer and add a rule for list_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 Postking Mcp. Nothing to install.
list_assets is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_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.
Set action: deny in the PolicyLayer policy for list_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.
list_assets is provided by the Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postking, and thousands of servers like it.
This server
Across the catalogue