AI agents call get_user_submitted_posts to retrieve information from PersonalizationMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description reducing confidence slightly, the tool name clearly indicates a retrieval operation ('get') that accesses personal user-generated content. This is a Read operation, but severity is elevated to 'high' because it accesses sensitive personal data across multiple social platforms without apparent access controls or filtering, creating significant privacy and context-misuse risks if an AI…
From the tool's definition Tool name 'get_user_submitted_posts' indicates retrieval of personal data from user accounts on platforms like Reddit, YouTube, or Bilibili mentioned in the server description. No modification or deletion is indicated.
Documented attack patterns abuse exactly the kind of access get_user_submitted_posts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PersonalizationMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_user_submitted_posts:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_submitted_posts": {}
}
}get_user_submitted_posts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_user_submitted_posts. It is categorised as a Read tool in the PersonalizationMCP MCP Server, which means it retrieves data without modifying state.
Register the Personalization MCP server in PolicyLayer and add a rule for get_user_submitted_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 PersonalizationMCP. Nothing to install.
get_user_submitted_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_user_submitted_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_user_submitted_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_user_submitted_posts is provided by the Personalization MCP server (yangliangwei/personalizationmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 88 PersonalizationMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
88 PersonalizationMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.