get_creator_posts
List stored social posts for a creator. When shown as a paid stub, calling this tool returns x402 payment requirements for the REST endpoint.
This record as markdown: /tools/com-getcims-mcp/get-creator-posts.md
What get_creator_posts does on Mcp
AI agents call get_creator_posts to retrieve information from Mcp 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 |
|---|---|---|---|
creatorId | number | Yes |
Parameters from the server's own tool schema.
Why get_creator_posts is rated Low
The primary function is Read—querying/retrieving stored posts without modification. However, the mention of payment requirements adds complexity: accessing this data may trigger financial obligations. Since the tool itself does not move money (that is handled by the API layer/authentication), and the core action is retrieval, Read is the correct category.
From the tool's definition Tool description states 'List stored social posts for a creator' which is a retrieval operation with no side effects. However, the note about 'x402 payment requirements for the REST endpoint' introduces a financial access control element.
Attacks that exploit this kind of access
The rule that runs get_creator_posts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_creator_posts, this is the rule to start with:
get_creator_posts 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 Mcp, apply this rule, and every get_creator_posts call is checked against it from then on.
Questions about get_creator_posts
List stored social posts for a creator. When shown as a paid stub, calling this tool returns x402 payment requirements for the REST endpoint. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
get_creator_posts accepts 1 parameter: creatorId. Required: creatorId. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for get_creator_posts: 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 Mcp. Nothing to install.
get_creator_posts 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 get_creator_posts 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 get_creator_posts. 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.
get_creator_posts is provided by the MCP server (https://api.getcims.com/functions/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue