Get the status of the ingestion pipeline: last run time, stats, next scheduled run, and any recent errors.
AI agents call get_pipeline_status to retrieve information from Paper Scout MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely queries and returns information about an internal ingestion pipeline's operational state (last run time, statistics, next scheduled run, errors). It has no side effects—it neither modifies data, executes code, deletes records, nor moves resources. The action is read-only introspection of system status.
From the tool's definition Tool description states 'Get the status...': retrieves pipeline metrics, timestamps, and error logs without modifying any data or triggering external operations.
Documented attack patterns abuse exactly the kind of access get_pipeline_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Paper Scout MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_pipeline_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_pipeline_status": {}
}
}get_pipeline_status 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 the status of the ingestion pipeline: last run time, stats, next scheduled run, and any recent errors. It is categorised as a Read tool in the Paper Scout MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Paper Scout MCP Server MCP server in PolicyLayer and add a rule for get_pipeline_status: 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 Paper Scout MCP Server. Nothing to install.
get_pipeline_status 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_pipeline_status 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_pipeline_status. 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_pipeline_status is provided by the Paper Scout MCP Server MCP server (jonradoff/paper-scout). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Paper Scout 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.
10 Paper Scout MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.