Get a consultant's blog posts / articles
AI agents call get_blogs to retrieve information from Mcp Cvpartner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
cv_id | string | — | CV ID; defaults to default_cv_id |
user_id | string | Yes | User ID |
Parameters from the server's own tool schema.
This tool retrieves existing blog posts or articles associated with a consultant. It performs a query operation with no side effects, no data modification, and no external execution. The action is read-only and returns information from the CVPartner system. Low severity reflects minimal risk; misuse would only expose publicly or semi-publicly available blog content.
From the tool's definition Tool name 'get_blogs' and description 'Get a consultant's blog posts / articles' indicate data retrieval with no modification or execution capability.
Attacks that exploit this kind of access
Get a consultant's blog posts / articles. It is categorised as a Read tool in the Mcp Cvpartner MCP Server, which means it retrieves data without modifying state.
get_blogs accepts 2 parameters: cv_id, user_id. Required: user_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Cvpartner MCP server in PolicyLayer and add a rule for get_blogs: 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 Cvpartner. Nothing to install.
get_blogs 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_blogs 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_blogs. 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_blogs is provided by the Mcp Cvpartner MCP server (@snokam/mcp-cvpartner). 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 →