get_recently_tabled_edms

What get_recently_tabled_edms does on UK Parliament MCP Server

AI agents call get_recently_tabled_edms to retrieve information from UK Parliament MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_recently_tabled_edms is rated Low

The tool retrieves public parliamentary data (EDMs are publicly tabled motions). The verb 'get' and the pattern matching sibling tools all performing read-only queries classify this as a Read operation. No data modification, deletion, or external effects occur. Confidence is 0.85 rather than higher due to empty description, though the name and server context provide clear intent.

From the tool's definition Tool name 'get_recently_tabled_edms' indicates retrieval of Early Day Motions (EDMs), a read operation. Context shows sibling tools are all query/retrieval operations (check_mp_vote, browse_*, get_* operations). EDMs are public parliamentary records.

The rule that runs get_recently_tabled_edms safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UK Parliament MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_recently_tabled_edms, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_recently_tabled_edms": {}
  }
}

Questions about get_recently_tabled_edms