Reads .txt or .docx documents and returns the content as plain text.
AI agents call read_document to retrieve information from JobApply MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple read operation on local documents to extract text content. It retrieves data without side effects, matching the Read category definition. Severity is low because misuse would only expose document contents, not cause destructive or financial harm. High confidence due to explicit description of read-only behavior.
From the tool's definition Tool name and description clearly indicate retrieval functionality: 'Reads .txt or .docx documents and returns the content as plain text.' No modification, deletion, execution, or financial operations are performed.
Documented attack patterns abuse exactly the kind of access read_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JobApply MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for read_document:
{
"version": "1",
"default": "deny",
"tools": {
"read_document": {}
}
}read_document 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.
Reads .txt or .docx documents and returns the content as plain text. It is categorised as a Read tool in the JobApply MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JobApply MCP Server MCP server in PolicyLayer and add a rule for read_document: 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 JobApply MCP Server. Nothing to install.
read_document 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 read_document 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 read_document. 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.
read_document is provided by the JobApply MCP Server MCP server (sakshee5/jobapply-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JobApply 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 JobApply MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.