get_post
Get detailed CMS post including content blocks, categories, and tags.
This record as markdown: /tools/io-favcrm-favcrm/get-post.md
What get_post does on FavCRM
AI agents call get_post to retrieve information from FavCRM 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 |
|---|---|---|---|
postId | string | Yes | The post ID |
Parameters from the server's own tool schema.
Why get_post is rated Low
This tool performs a data retrieval operation on CMS post content. It queries and returns existing data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker could only exfiltrate post content that may already be accessible or known. No data is altered, no financial impact occurs, and no external commands are executed.
From the tool's definition The tool 'get_post' retrieves detailed CMS post information including content blocks, categories, and tags. The verb 'get' and descriptor 'retrieves' indicate a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_post safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_post, this is the rule to start with:
get_post 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 FavCRM, apply this rule, and every get_post call is checked against it from then on.
Questions about get_post
Get detailed CMS post including content blocks, categories, and tags. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
get_post accepts 1 parameter: postId. Required: postId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for get_post: 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 FavCRM. Nothing to install.
get_post 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 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. 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 is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue