Read or update the LinkedIn post viewer filters. Filter state syncs between MCP and the React viewer UI.
AI agents use viewer_filters to create or update resources in LinkedIn-Posts-Hunter-MCP-Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LinkedIn-Posts-Hunter-MCP-Server environment.
The tool performs both read and write operations on filter state. While reading filter configuration is a Read operation, the explicit 'update' capability elevates this to Write category. Updating filters could alter what posts are retrieved and displayed, affecting the behavior of linked tools like search_posts. This is reversible configuration change (not destructive), so Write is appropriate.
From the tool's definition Tool description states 'Read or update the LinkedIn post viewer filters', with explicit mention of update capability. The dual read/write nature with state synchronization indicates modification of filter configuration.
Documented attack patterns abuse exactly the kind of access viewer_filters gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn-Posts-Hunter-MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for viewer_filters:
{
"version": "1",
"default": "deny",
"tools": {
"viewer_filters": {
"limits": [
{
"counter": "viewer_filters_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}viewer_filters stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read or update the LinkedIn post viewer filters. Filter state syncs between MCP and the React viewer UI. It is categorised as a Write tool in the LinkedIn-Posts-Hunter-MCP-Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LinkedIn-Posts-Hunter-MCP-Server MCP server in PolicyLayer and add a rule for viewer_filters: 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 LinkedIn-Posts-Hunter-MCP-Server. Nothing to install.
viewer_filters is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the viewer_filters 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 viewer_filters. 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.
viewer_filters is provided by the LinkedIn-Posts-Hunter-MCP-Server MCP server (kevin-weitgenant/linkedin-posts-hunter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LinkedIn-Posts-Hunter-MCP-Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 LinkedIn-Posts-Hunter-MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.