List post history with optional filters. Returns posts with their status, content, platforms, and scheduling info.
AI agents call get_post_history to retrieve information from Ayrshare Unofficial MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists existing post history data with optional filtering. It has no side effects, does not modify data, does not execute external operations, and does not involve financial transactions. It is purely a read operation that satisfies the 'Read' category definition: retrieves or queries data with no side effects.
From the tool's definition Tool name 'get_post_history' and description 'List post history with optional filters. Returns posts with their status, content, platforms, and scheduling info' indicates a retrieval operation that queries historical data without modification.
Attacks that exploit this kind of access
List post history with optional filters. Returns posts with their status, content, platforms, and scheduling info. It is categorised as a Read tool in the Ayrshare Unofficial MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Ayrshare Unofficial MCP Server MCP server in PolicyLayer and add a rule for get_post_history: 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 Ayrshare Unofficial MCP Server. Nothing to install.
get_post_history 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_post_history 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_post_history. 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_post_history is provided by the Ayrshare Unofficial MCP Server MCP server (yardz/ayrshare-unofficial-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →