This record as markdown: /tools/io-github-bitsandtea-postking-mcp/trends-list.md
What trends_list does on Postking Mcp
AI agents call trends_list 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 trends_list is rated Low
The tool appears to retrieve or query trend data for content creation purposes, consistent with a social media management platform's Read category functionality. Without a description, confidence is moderately high based on naming convention and context of sibling tools. No evidence of data modification, deletion, code execution, or financial impact.
From the tool's definition Tool name 'trends_list' indicates a listing/retrieval operation. The pattern matches sibling tools like 'billing_list_packs' and 'billing_list_tiers' which are clearly Read operations.
Attacks that exploit this kind of access
The rule that runs trends_list 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 trends_list, this is the rule to start with:
trends_list 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 trends_list call is checked against it from then on.
Questions about trends_list
trends_list is a read tool on the Postking MCP server. 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 trends_list: 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.
trends_list 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 trends_list 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 trends_list. 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.
trends_list 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