Get scheduled and published posts from Hootsuite.
AI agents call get_posts to retrieve information from Hootsuite MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves post data without creating, modifying, deleting, or executing any operations. It is a read-only operation that has no side effects on the system or data state. Low severity due to minimal blast radius if misused—an AI agent would only retrieve information already accessible to the authenticated user.
From the tool's definition Tool name 'get_posts' and description 'Get scheduled and published posts from Hootsuite' indicate retrieval of existing data with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get scheduled and published posts from Hootsuite. It is categorised as a Read tool in the Hootsuite MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Hootsuite MCP Server MCP server in PolicyLayer and add a rule for get_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 Hootsuite MCP Server. Nothing to install.
get_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_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_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_posts is provided by the Hootsuite MCP Server MCP server (lokimcpuniverse/hootsuite-mcp-server). 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 →