Return the latest writer-pipeline job for a (sessionId, section).
AI agents call get_writer_pipeline_status to retrieve information from Science Ai without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries the status of an existing writer-pipeline job for a given session and section. It is a read-only operation that fetches data without creating, modifying, deleting, or executing any operations. The verb 'return' and 'status' clearly indicate data retrieval rather than any action that would change system state.
From the tool's definition Tool returns status information via 'Return the latest writer-pipeline job' with no modification capability indicated. Pure query operation with no side effects.
Attacks that exploit this kind of access
Return the latest writer-pipeline job for a (sessionId, section). It is categorised as a Read tool in the Science Ai MCP Server, which means it retrieves data without modifying state.
Register the Science Ai MCP server in PolicyLayer and add a rule for get_writer_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 Science Ai. Nothing to install.
get_writer_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_writer_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_writer_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_writer_pipeline_status is provided by the Science Ai MCP server (selfpy/science-ai-mcp-server). 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 →