This record as markdown: /tools/io-github-bitsandtea-postking-mcp/list-jobs.md
What list_jobs does on Postking Mcp
AI agents call list_jobs to retrieve information from Postking Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_jobs is rated Low
The tool lists existing jobs with no indication of creating, modifying, deleting, or executing actions. Despite an empty description, the naming convention strongly suggests this retrieves job status/history data without side effects. Confidence is moderate (0.8) rather than high due to the lack of descriptive detail, but the semantic meaning of 'list_jobs' is unambiguous.
From the tool's definition Tool name 'list_jobs' indicates a query/list operation that retrieves job records. The 'list' prefix is characteristic of Read operations (search, list, get, fetch).
Attacks that exploit this kind of access
The rule that runs list_jobs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postking Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_jobs, this is the rule to start with:
list_jobs 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 Postking Mcp, apply this rule, and every list_jobs call is checked against it from then on.
Questions about list_jobs
list_jobs is a read tool on the Postking MCP server. It is categorised as a Read tool in the Postking Mcp MCP Server, which means it retrieves data without modifying state.
Register the Postking MCP server in PolicyLayer and add a rule for list_jobs: 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 Postking Mcp. Nothing to install.
list_jobs 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 list_jobs 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 list_jobs. 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.
list_jobs is provided by the Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postking, and thousands of servers like it.
This server
Across the catalogue